For enterprises dependent upon on-premises datacenters, effectively managing development clusters with Kubernetes has its own challenges. While these challenges can certainly be overcome, not addressing them early on in your Kubernetes adoption process can lead to major issues down the road.
Here are five steps every enterprise should take before attempting to utilize Kubernetes in their datacenter:
1. Choose the right cluster orchestrator
Selecting and familiarizing yourself with the right cluster orchestrator to fit your needs is critical. Not only will it make standup and managing additional clusters feasible, it will provide you with a uniform process and general overview to downstream clusters.
As for which orchestrators we recommend, it depends on the roadmap of the client. If your roadmap includes the cloud in a hybrid solution, we suggest Google Anthos—especially if the Google Cloud Platform (GCP) is your chosen platform—or Rancher. For strictly on-premises, the Pivotal Kubernetes Engine (PKE) is usually the way to go.
2. Have a plan for nodes
When employing Kubernetes in your datacenter, make sure your nodes are replaceable because utilizing worker nodes for storing files, configuration, and persistent data pods is a recipe for easy failure.
Overall, your pods should never depend on the underlying hardware they run on, but rather, they should be capable of running on any worker node in the cluster.
Achieving this mostly entails making sure that workloads are not mounting anything from the underlying host, so that if pods are moved to another host they will be able to be put back up.
3. Develop an upgrade strategy
Due to being open-source, Kubernetes is always experiencing changes brought about by the community. This is part of why the solution is so powerful, but it also means that being able to upgrade without downtime is critical for your success.
Cloud providers generally provide an upgrade mechanism for managed clusters. But for your on-premises datacenter, you want to make sure you have a patch and upgrades strategy in place and that you use that strategy to test upgrades often and early.
4. Develop backup procedures
In the unlikely event that your ETCD cluster loses quorum, or the underlying VMs are lost, it’s important to have a backup of your data.
In order to be able to restore the previous state, you should set up a backup routine that occurs regularly, depending on how much retention is necessary and how often ETCD data changes via API calls.
5. Find the hardware that works best for you
In general, we are agnostic when it comes to hardware, so for managing Kubernetes in your datacenter, we recommend sticking with the hardware you’re most comfortable with.
One recommendation we do often make, however, is that for those enterprises that choose Anthos and GCP for Kubernetes, Dell EMC HCI hardware provides an integrated platform tailored to help you get the most out of Anthos as an orchestrator.
Keep up with Redapt
- Enterprise Infrastructure
- Data & Analytics
- Cloud Adoption
- Cloud Native
- Workplace Modernization
- Code Development
- Multi-Cloud Operations
- Google Cloud Platform (GCP)
- Tech We Like
- Security & Governance
- Dell EMC
- IoT and Edge
- Managed Services
- Business Transformation
- Microsoft Azure
- Emerging Tech