#Gradient puzzle upgrade

вЂњBut how do you know what it looks like a month from now?вЂќ Even if you donвЂ™t touch the cluster again, he noted, вЂњan installed add-on with high-enough privileges could end up changing foundational configuration without you knowing about it.вЂќ

вЂњYou know what your cluster looks like today, when you built it,вЂќ Budhani said. Here, according to Budhani and other experts, are five pillars of Kubernetes Ops: Cluster Standardization and Lifecycle Management In fact, the fear of dealing with that complexity can keep organizations from moving toward multi-cloud solutions in the first place and could lead to vendor lock-in that prevents an organization from realizing its business goals.Д«ut the key areas that need attention remain the same, no matter where youвЂ™re deploying your applications. For organizations that need to deploy into multi-cloud or hybrid environments, this complexity -В and the challenges of keeping tabs on all the moving parts - compounds. On an ongoing basis, managing your Kubernetes operations requires keeping track of a number of things. вЂњBy definition, if youвЂ™re building it again, and again, you arenвЂ™t following the first rule of DevOps: Automate everything.вЂќ What Does Day 2 for Kubernetes Ops Look Like? вЂњWeвЂ™re not aligning to the North Pole that we all agreed was the right thing to do вЂ“ automation,вЂќ Budhani said. Day 2 is about what needs to happen to keep the lights on while the underlying technologies each require custom strategies for their governance, operational security and visibility in a fully automated fashion.вЂќДЄn overarching issue he sees is that not enough enterprises are using what he calls вЂњautomation with governanceвЂќ - the developer velocity and freedom from unnecessary toil that cloud native architecture promises, coupled with the checks and balances that organizations need to control access to critical data, applications and infrastructure, and control cloud costs. вЂњSo, you have to manage the lifecycle of your Kubernetes cluster, the lifecycle of each of these tools, the lifecycle of your applications, centralized policy and access management as new internal teams deploy more apps, a disaster recovery strategy for each app, charge-back strategies, and more.вЂќ Every so often, each of these tools will need to be updated across all the clusters,вЂќ Budhani said. вЂњAll these tools, they follow their own lifecycle. Then thereвЂ™s the hodgepodge of tools in the cloud native ecosystem that your organization uses to operationalize Kubernetes, each of which also regularly requires upgrades and attention. First, thereвЂ™s the matter of the skills gap - eight years into the Kubernetes era and there still arenвЂ™t enough engineers who know enough about the K8s ecosystem.ДЄ lack of in-house skills is the top challenge that companies encounter when adopting containers and Kubernetes, according to a survey released last June by Canonical. The pain has a number of root causes, Budhani said. вЂњWe need a moment of catharsis in this industry.вЂќ Why Is Day 2 So Painful? вЂњWeвЂ™ve got to be honest about the pain here,вЂќ Budhani said. These problems can all be grouped under the heading of вЂњDay 2.вЂќ And Day 2 can mean a never-ending headache for site reliability engineers (SRE) and IT operations engineers.

#Gradient puzzle upgrade

вЂњHow do I manage access to my clusters? WhatвЂ™s the policy model that IвЂ™m going to use across all my environments? What add-ons must I always have in the standard blueprint for my production clusters? What is my strategy to deploy applications that belong to multiple business units? IвЂ™ve got to upgrade all my clusters soon since IвЂ™m already three versions behind across the board - how do I do that?вЂќ вЂњWhether youвЂ™re talking to a high-tech company, or a financial services company, a healthcare company, or a retailer running apps at the edge, the problems are all the same,вЂќ Budhani, CEO and co-founder of Rafay, a Kubernetes operations platform, told The New Stack. Haseeb Budhani has seen it happen again and again.ДЄn organization undertakes a move to adopt cloud native technologies and implements Kubernetes.ДЄnd then things start to get вЂ¦ interesting.Д¬lusters multiply. Rafay sponsored this article for The New Stack.