As Kubernetes continues to gain popularity, engineers have to know how Kubernetes works, and why it might make sense in their environment.
A thread 🧵
Here are a few questions that you should ask yourself
- What benefits does Kubernetes bring to environments?
- What do technologies like containerization do for organizations?
- Does Kubernetes actually help teams?
In this blog post, I’ll provide some basic background on containers and Kubernetes.
Also, some suggestions for how to think about Kubernetes for infrastructure pros.
Are you using Ingress Controllers in your Kubernetes environment?
If not, let's break down what they are.
A thread 🧵
At a high level, Ingress Controllers are:
- Specify multiple paths
- Specify multiple services
All in one load balancer.
Let's break it down.
ingress Controllers are just like any other Controller in a Kubernetes environment. They confirm that the current state is the desired state for the deployment.
If so, ensure that you're comfortable in the following domains:
- Kubernetes storage
- Troubleshooting system components (control planes and worker nodes)
- Pod and other workload scheduling (including high availability)
(cont)
- Cluster architecture (building out clusters using Kubeadm)
- All of the control plane and worker node components (Etcd, Controller, Scheduler, etc.)
- RBAC
- Cluster security
- Kubernetes services and networking
Are you using GitOps today in your Kubernetes cluster?
If not, let me show you how to get a GitOps operator up and running in under EIGHT minutes.
a thread 🧵
Using Flux (a popular GitOps operator), you can:
- Install the controller on a Kubernetes cluster
- Connect to a GitHub org
- Point to a source control repo
- Deploy an app
- Have it managed by GitOps
in less time than you probably think.
If you're not familiar with GitOps, here's a quick breakdown.