What Does Production Ready Really Mean for a Kubernetes Cluster?
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 its e …
| Talk Title | What Does Production Ready Really Mean for a Kubernetes Cluster? |
| Speakers | Lucas Käldström (Student, Contracting) |
| Conference | KubeCon + CloudNativeCon Europe |
| Conf Tag | |
| Location | Copenhagen, Denmark |
| Date | Apr 30-May 4, 2018 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
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
