Hello Cloud Gurus,
I have been preparing for the Google Cloud Associate Engineer test. I have been following along with the theory, labs in the console and the shell. Things are progressing great.
I hit a road block when I get to "The Kubernetes Course"
I dont have prior experience of working in cloud environment and I started taking the course (From Nigel) that is linked with this course.
Although I get a good idea of topics that I have covered so far, it does seem challenging to me. For example he has "yml files" with configured loadbalancers and storage classes etc but I have no idea how he built them. Should I be concerned about that? I dont know.
I would like to learn it just not for the sake of this test but to be able to make sense out of how to use it.
Also read the Exam Guide to See what are the topics that I should focus on: Here it is
4.2 Managing Google Kubernetes Engine resources. Tasks include:
Viewing current running cluster inventory (nodes, pods, services)
Browsing the container image repository and viewing container image details
Working with node pools (e.g., add, edit, or remove a node pool)
Working with pods (e.g., add, edit, or remove pods)
Working with services (e.g., add, edit, or remove a service)
Working with stateful applications (e.g. persistent volumes, stateful sets)
Working with management interfaces (e.g., Cloud Console, Cloud Shell, Cloud SDK)
I am not sure how exactly this all is achieved.
Would anybody point me to what in your opinion is the best suggestion ? Sure I can create a cluster and run kubectl in the shell but what really should I do after that ?
Sorry about the long post, I really feel stuck with this. Thanks for your time and help.
Hello, Hiasad! Kubernetes (K8s) definitely is an important part of the scope for an Associate Cloud Engineer, so I’m glad you’ve reached out. And I’m glad you’ve felt like you’ve been progressing well aside from that.
I think a great thing for you to do would be to dig a bit deeper into some of those YAML files to demystify them. Those files are just a way of telling the K8s system what we want from it–what we want it to accomplish on our behalf–so it’s a kind of instructions we give it. But the instructions are not imperative, like "Do this; do that". Instead, these instructions are declarative–like "I want this; I want that"–and then K8s figures out what actions need to be taken to achieve those results. If you have this in mind when you look back to some YAML files, do they make more sense?
I hope this helps!