What You Will Be Doing
What You Will Learn
- What a DevOps engineer does at Junovy
- What your first weeks will look like
- What you are not expected to know yet
Your Role in One Sentence
You will keep the Junovy platform running, deploy applications for clients, and improve the infrastructure over time.
What DevOps Means Here
DevOps is the bridge between writing code and running code. In game terms: you are not the game designer or the player. You are the person who makes sure the servers are online, the builds deploy correctly, and the players can connect.
At Junovy, your daily work falls into these categories:
| Category | What It Looks Like | How Often |
|---|---|---|
| Client onboarding | Set up a new namespace, deploy their apps | A few times per month |
| App updates | Bump an image version, push to Git, verify | Weekly |
| Troubleshooting | A client's app is down, find out why, fix it | As needed |
| Infrastructure | Update Kubernetes components, improve configs | Ongoing |
| Monitoring | Check dashboards, respond to alerts | Daily |
What You Are NOT Expected to Know Yet
This is important. You are joining with a computer science background and game development skills. That is valuable. You are not expected to already know:
- Kubernetes (you will learn it in Chapter 3)
- Docker (Chapter 2)
- GitOps or Flux CD (Chapter 4)
- Terraform or Ansible (not covered in this book, comes later)
- Linux system administration (you will pick it up as you go)
Your First Weeks
| Week | Focus |
|---|---|
| Week 1 | Read Chapters 1-4 of this book, set up your tools (Chapter 6) |
| Week 2 | Read Chapters 5-8, explore the repos with guidance |
| Week 3 | Do the Godot project (Chapter 9) with support |
| Week 4 | Do the Faeries project (Chapter 10) with less support |
| After | Start handling real tasks with the Day-to-Day Workflows (Chapter 11) |
There is no rush. Ask questions. Re-read pages. The book is designed so you can come back to any section later.
Key Takeaways
- Your job is to keep the platform running and deploy apps for clients
- You are not expected to know Kubernetes, Docker, or GitOps yet
- The first four weeks have a structured learning path
What Is Next
Next up: How This Book Works where you will learn about the structure of every page so you always know what to expect.