I'm looking for some motivation to start learning Kubernetes. Right now, I'm using Docker for my services and leveraging Azure Container Apps for orchestration, which seems pretty flexible for my needs. I also use various Azure services like queues, storage, and RBAC. At the moment, I don't see any limitations with my current stack.
I thought about diving into Kubernetes to gain more control and flexibility compared to managed solutions, but I've run into a few concerns:
1. Cost: Kubernetes seems like it could be more expensive since it requires at least one VM running 24/7 for the control plane, while Azure Container Apps offers a serverless control plane that is more budget-friendly.
2. Redundancy: I feel like using Kubernetes overlaps with my Infrastructure as Code tools like Bicep or Terraform when it comes to resource management, and that feels unnecessary.
3. Managed Services: With Azure Kubernetes Service (AKS) still being a managed option, I wonder if there's any real advantage to using Kubernetes over Container Apps, especially considering the cost of node pool VMs.
I'm finding it hard to stay motivated to learn Kubernetes and can't see myself recommending it for real projects. I'd love to hear from anyone who has more experience where I might be going wrong in my thinking about this!
7 Answers
Before you dive into Kubernetes, what's your ultimate goal? Are you learning it for a hobby, career advancement, or a specific project? Having clarity on your objectives can really help with motivation!
I get that you feel it's duplication of IaC, but consider it as a cloud-agnostic API. Kubernetes can abstract a lot of the hassle, and even if you're not using everything the cloud offers, it's good to have that flexibility.
Honestly, if you don't have a strong need for Kubernetes, it might be better to stick with what you have. Kubernetes shines in more complex environments where you need better control. If Container Apps meets your needs, there's no harm in using it!
You could go for a managed control plane like AKS, which can make your life easier. Also, consider that Kubernetes and Container Apps can have different pros and cons, like costs and limitations on features. It just depends on the specific use case you have in mind.
If you find Kubernetes intimidating, start with something simpler like k3s for your local learning. It can give you the Kubernetes experience without some of the complexities of the full setup!
There's absolutely nothing wrong with just wanting to learn! Kubernetes is designed for enterprise environments, but if you're fascinated by it, that's reason enough to get started. You might want to try a home lab setup with Minikube or some cloud credits for hands-on experience. Learning is part of the IT journey!
I started with Docker too, but once I dove into Kubernetes on a couple of Raspberry Pis, it changed everything for me. The hands-on experience alongside GitOps really clicked. It's challenging, but if you find the right project, it can be incredibly rewarding!
Exactly! I think having a project in mind might help too, something where Kubernetes would really shine.