This talk was given at KubeCon Europe 2018 in Copenhagen
Video recording: https://youtu.be/EjSiZgGdRqk
Sched page: http://sched.co/Dqvh
Slides can be viewed online here: https://docs.google.com/presentation/d/1oaBm68OQmz3xW1t5trc0i6MNbaxVpZ_2QN58Nfgelpo/edit#slide=id.p
Abstract: How would you describe and set up a “production ready” Kubernetes cluster? How are the buzzword terms “production ready” and “highly available” defined anyway?
Can a cluster be created so that it’s end-to-end secured, has no single points of failure, is upgradable without control plane downtime and is conformant?
If you have access to automated infrastructure, e.g. via a Cluster API controller, you should be able to do CI testing of your cluster, as well as CD of new configuration and versions. Some call this pattern “GitOps”; to write the desired cluster state declaratively and let a controller reconcile the cluster state.
By the end of this talk, you should be able to tell:
- What you may consider a “production ready” cluster to be and identify the moving parts
- How to secure cluster component traffic
- How to minimize failure points
- How to manage clusters using the Cluster API