Read on Twitter
Kubernetes (K8s) is an in-demand technology! 
https://abs.twimg.com/emoji/v2/... draggable="false" alt="đ" title="Rakete" aria-label="Emoji: Rakete">
Let me give you some resources to get started and add my own opinion at what you should learn as a developer, and what not!
https://abs.twimg.com/emoji/v2/... draggable="false" alt="đ§”" title="Thread" aria-label="Emoji: Thread">https://abs.twimg.com/emoji/v2/... draggable="false" alt="đ" title="RĂŒckhand Zeigefinger nach unten" aria-label="Emoji: RĂŒckhand Zeigefinger nach unten">
Let me give you some resources to get started and add my own opinion at what you should learn as a developer, and what not!
This is the official Kubernetes website.
It is a really great point to get started with K8s and its ecosystem.
Especially https://kubernetes.io/docs/tutorials/kubernetes-basics/">https://kubernetes.io/docs/tuto... will work you through the process of deploying your first containerized application!
freecodecamp">https://www.freecodecamp.org/news/lear... nearly never disappoints us with free learning resources.
And it doesn& #39;t disappoint this time, too.
I really like this guide because it explains the process of going from zero to "I& #39;m done!" in a great way!
Interactive">https://www.katacoda.com/courses/k... sessions to learn working with Kubernetes.
The courses mostly focus on one thing at a time.
They offer a free 10-day trial!
Maybe">https://www.edx.org/course/in... you want to learn Kubernetes from the Linux Foundation?
If so, they have a course for you, and it doesn& #39;t disappoint in any way.
My own to cents:
Even in times of serverless and other awesome offerings, it doesn& #39;t hurt having a little knowledge about Kubernetes.
Not all workloads are suited for serverless, and sometimes you need more flexibility.
At this point, K8s enters the arena.https://abs.twimg.com/emoji/v2/... draggable="false" alt="âïž" title="Gekreuzte Schwerter" aria-label="Emoji: Gekreuzte Schwerter">
Even in times of serverless and other awesome offerings, it doesn& #39;t hurt having a little knowledge about Kubernetes.
Not all workloads are suited for serverless, and sometimes you need more flexibility.
At this point, K8s enters the arena.
Gone are the times where the only valid choice you have is setting up a cluster on your own (which is a science for itself sometimes, btw).
You can still go for a managed K8s offering like:
- AWS: EKS
- Azure: AKS
- Google Cloud: GKE
You can still go for a managed K8s offering like:
- AWS: EKS
- Azure: AKS
- Google Cloud: GKE
So what should you know as a developer?
1. You should get comfortable with what a Pod is and how to deploy one.
2. Learn about Services and what they actually do for you.
3. Get comfortable with Deployments!
4. Get to know ConfigMaps and how to pass properties to your app.
1. You should get comfortable with what a Pod is and how to deploy one.
2. Learn about Services and what they actually do for you.
3. Get comfortable with Deployments!
4. Get to know ConfigMaps and how to pass properties to your app.
5. Spend some time learning about different types of secret stores and why they are so important before you save clear text passwords in your ConfigMaps!
6. Revise everything you knew about how to write software, and then take a look at 12-factor apps -> http://12factor.net"> http://12factor.net
6. Revise everything you knew about how to write software, and then take a look at 12-factor apps -> http://12factor.net"> http://12factor.net
"And what else?" you might now ask.
Everything listed above is the minimum a developer should know if they want to work with Kubernetes.
You could learn more if you like, but you shouldn& #39;t learn less, at least if you plan to really work in a K8s environment.
Everything listed above is the minimum a developer should know if they want to work with Kubernetes.
You could learn more if you like, but you shouldn& #39;t learn less, at least if you plan to really work in a K8s environment.
Larger companies nowadays have the money to actually pay dedicated DevOps engineers to do the really heavy lifting and working with K8s.
But depending on where you work (or you don& #39;t) it might be pretty clever to learn more about K8s, as it might improve chances for your career.
But depending on where you work (or you don& #39;t) it might be pretty clever to learn more about K8s, as it might improve chances for your career.
I myself am not a huge fan of giving developers even more responsibility than they already have.
There is so much more to K8s than only what I listed above and told you to learn.
There is an ecosystem full of tools, addons, and advanced techniques to get the most out of K8s.
There is so much more to K8s than only what I listed above and told you to learn.
There is an ecosystem full of tools, addons, and advanced techniques to get the most out of K8s.
We haven& #39;t covered techniques such as GitOps here and putting everything into code that we possibly can, and then automating it to the point where manual labor (except committing and pushing a change to a remote repository), but this is pretty advanced stuff. https://abs.twimg.com/emoji/v2/... draggable="false" alt="đ" title="LĂ€chelndes Gesicht mit lĂ€chelnden Augen" aria-label="Emoji: LĂ€chelndes Gesicht mit lĂ€chelnden Augen">
*where manual labor isn& #39;t necessary, anymore
