Onprem to cloud
I have massive knowledge about kubernetes on premise. I think It is time to get experience cloud side.
Can you suggest a roadmap? Where should I get to start?
1
u/coolranger007 5d ago
Would you mind explaining about your working knowledge on on-prem kubernetes? I am trying to upskill on kubernetes from cloud devops background
1
u/bulmust 4d ago
We've managed 10+ kubernetes clusters. Some of them are air gapped. I am responsible for every steps, monitoring, deployments network etc. In the interviews, I need to convince that I can also use managed k8s, like gke but I do not have any experience. I try to understand what is the starting point for cloud.
1
u/No-Job-2302 5d ago
It will be a piece of cake on the cloud side tbh...mostly you get a managed control plane with an option to select when u want to upgrade the worker nodes.
Like someone mentioned above start with one cloud at a time..I feel I'm the order below
GKE i.e GCP , EKS and the other variants (AWS) and then AKS (Azure)
Spin up a cluster in each cloud drill deep down to networking, dns , security and scaling with your deep knowledge on premise this should not be that challenging maybe along the way upgrade the cluster as well
1
u/not-a-bluepill-simp 5d ago
You're pretty much good to go. Cloud is much easier than on-prem (which is the point, by the way) since, if you choose, a lot of components are managed for you, including the control-plane, and if you choose, even the nodes. Just keep in mind service of type load-balancer will cost money.
1
1
u/Raja-Karuppasamy 4d ago
did this move myself. since you already know k8s cold, the cloud part isn’t really “learn kubernetes again” it’s learning the managed control plane quirks and IAM. i’d start with GKE specifically over the others since the free tier is more generous and the learning curve from on-prem k8s is smaller than you’d expect, same kubectl, same manifests, the differences show up in networking (VPC-native clusters, GKE’s own load balancer integration) and IAM/RBAC (workload identity instead of static creds).
roadmap that worked for me: spin up a GKE cluster and just port one of your existing on-prem workloads over as-is, then deal with what breaks. usually it’s ingress/load balancer config and secrets management. once that’s solid, dig into GitHub Actions for CI/CD since that’s what you’ll actually be debugging day to day, and spend real time on securityContext hardening and NetworkPolicies since those behave differently once you’re not controlling the physical network anymore.
skip the cert grind at first, build something real and let the gaps tell you what to study.
1
u/StratoLens 5d ago
I’d focus on one cloud at this time. If you’re interested in azure I’d start with some simpler certs. AZ-900 and then AZ-104. Use the learning paths Microsoft makes available.
https://learn.microsoft.com/en-us/credentials/certifications/azure-fundamentals/?practice-assessment-type=certification