Original guide: 04-certificate-authority.md Thoughts I had while doing this Before the actual step though, here are some stuff I learned or was thinking about along the way: Kubernetes is starting to feel like a miniaturized version of an entire IT infrastructure.
![[Lab Notes] Kubernetes the Hard Way, For Real This Time (Step 04)](/api/proxy/image?url=https%3A%2F%2Fmedia2.dev.to%2Fdynamic%2Fimage%2Fwidth%3D1200%2Cheight%3D627%2Cfit%3Dcover%2Cgravity%3Dauto%2Cformat%3Dauto%2Fhttps%253A%252F%252Fdev-to-uploads.s3.us-east-2.amazonaws.com%252Fuploads%252Farticles%252Fc1s2o7vfj3t7v9b2r6e4.png)
Original guide: 04-certificate-authority.md Thoughts I had while doing this Before the actual step though, here are some stuff I learned or was thinking about along the way:
Kubernetes is starting to feel like a miniaturized version of an entire IT infrastructure.
Every Kubernetes component (API server, kubelet, etc.) is like another service on the network, and they all need to trust each other the same way any two servers would.
The page is ready to read now. The fuller skim-friendly version will appear here automatically.
Original guide: 04-certificate-authority.md Thoughts I had while doing this Before the actual step though, here are some stuff I learned or was thinking about along the way: Kubernetes is starting to feel like a miniaturized version of an entire IT infrastructure. Every Kubernetes component (API server, kubelet, etc.) is like another service on the network, and they all need to trust each other the same way any two servers would.
Steps 01-03 are already done, this covers step 04. It's like Kubernetes took that same idea and asked "hey we already abstracted compute, why not abstract the whole infrastructure?" Generating and installing all these certs felt exactly like setting up TLS between a bunch of servers so they can trust each other.
Open the app view to save this story, compare related coverage, and continue from the same source.