We're in the process of transitioning our legacy software to a cloud-based environment using Kubernetes. However, we still need a solution for deploying a Kubernetes version on our customers' on-premises setups. An architect in our team suggests that we should deploy a Kubernetes cluster on the customers' infrastructure using Rancher or Kubespray, which also means we'd have to handle the cluster maintenance ourselves. My concern is that we don't even have a clear picture of what's running underneath their VMware/RedHat environments. I believe we should just provide the necessary Helm charts and Docker images instead. I'm confused as to why there's a push for us to manage Kubernetes on-site at clients when we're not an infrastructure software company. I've seen OVA Appliance-based software being deployed in this way, but never a full cluster deployed with Rancher, along with the applications it hosts. Has anyone encountered software that follows this approach?
2 Answers
Deploying Kubernetes on customer infrastructure can be a major hassle. If you don’t have full control over their environments, like waiting on network permissions or provisioning new nodes, it can lead to delays and frustration. But hey, if they're paying well for it, it might be worth considering! Just be prepared for the complications.
It boils down to your contract with the customer. If it’s in there, you might not have a choice but to deliver it, even if it seems unreasonable. If it’s not, you might want to renegotiate to either exclude that requirement or get a better deal for the extra work. Bad management shouldn't force you into extra responsibilities.
You’re right! There’s actually no contract for this. They aren’t even aware of the implications of this approach.