Normal view

Yesterday — 5 June 2026Tech

Is it a problem if I'm only learning on-prem Kubernetes and never touch AWS/Azure?

I'm a junior DevOps engineer and I'm a bit worried about the direction I'm learning in, so I wanted to get some outside opinions.

At my job (and in my personal projects) I work almost entirely with on-prem / self-managed infrastructure. The stack I'm learning is roughly:

  • K3s (self-managed Kubernetes on VMs)
  • Cilium as the CNI (incl. Gateway API)
  • ArgoCD for GitOps
  • Ansible for provisioning
  • Terraform
  • Longhorn for storage, CloudNativePG for Postgres
  • etc...

The thing is, I've never used a public cloud — no AWS, Azure, or GCP. No EKS/AKS/GKE, no managed databases, no Terraform against a cloud provider. Everything I do is bare VMs and self-hosted components.

My question: is this a problem? A few things I'm wondering:

  1. Will I be at a disadvantage in the job market by not knowing the big clouds?
  2. Are the concepts I'm learning (Kubernetes internals, networking, GitOps, storage, etc.) transferable to cloud-managed setups, or is it a different world?
  3. Should I make an effort to learn a cloud on the side, or is deep on-prem experience valuable enough on its own?

I genuinely enjoy the on-prem / "build it yourself" side of things, I just don't want to accidentally box myself in. Any honest perspective from people who've been in the field longer would be really appreciated. Thanks

submitted by /u/Low-Response-5711 to r/devops
[link] [comments]
❌
❌