I’d like to label myself as a kubernetes expert and software architect in two years.
Like everyone in container world, I have a lot of pleasures consuming kubectl. And behind the scene, I’m even more amazed for how typical K8S solutions are designed and implemented.
If you’re also interested, here is a blog series for you. Check it out, and discuss with me!
From bottom to up. From bare metal to the beginning to the final solution. There are lots of interesting questions and amazing ideas to learn and discuss.
It could be very helpful for you, if your oragnization is heavily using containers in either development or deployment phases. And the experience should also be useful, as long as you’re working at infra domain. No matter private clouds or public clouds.
In this blog series, we focus on below things:
- What are the domain languages and concepts?
- What factors we should consider?
- What are the known issues?
- What are the best practices?
Anti-goal: It shouldn’t share any confidential information from my current employer.
Layers & Components
At very high level, different layers of typical K8S solutions can be illustrated as below figure.
- Hardware & Infra
- K8S vendor
- CNCF k8s upstream
- Business add-on
- Episode: Public K8S Solution VS On-Prem solution
- Episode: K8S Solution – Control Plane (TBD)
- Episode: K8S Solution – Virtualization & Bare Metal (TBD)
- Episode: K8S Solution – Management Console (TBD)
- Episode: K8S Solution – Life Cycle Management (TBD)
- Episode: K8S Solution – Networking (TBD)
- Episode: K8S Solution – Authentication & Authorization (TBD)
- Episode: K8S Solution – Integration test (TBD)