What do you need for a Kubernetes cluster before you can call it “production ready”? How do you define “production ready” and what does a “highly available” cluster mean anyway? Can a cluster be created so that it’s secured from end-to-end, has zero single points of failure, and is upgradable without any control plane downtime?
Although a cluster can be production ready when it’s good enough to serve traffic, many operators and SREs would agree that there are a minimum set of requirements you need before you can safely declare your cluster ready for commercial traffic.
If you are just getting started or maybe you’ve set up a proof of concept and want to see what you’re missing, then these convenient checklists can help your team reliably operate and build applications for Kubernetes clusters in the cloud.
Download these comprehensive checklists, one for your cluster and another for your applications, to help determine your internal readiness and to gain an understanding of which areas you need to update or otherwise pay attention to.
Have questions on what you need to create a cloud native platform?
Weave GitOps reduces complexity through configuration management, automation and operations tooling. With GitOps configuration management, teams can define a standard installation of Kubernetes and automate the deployment of new nodes with a predefined template. It also simplifies additional cluster installations, since Kubernetes is already preconfigured and any applications running on top of it are also predefined.