4 ms·

imo running k8s in the cloud makes no sense. If you've already setup on prem servers, load balancers, config management, patching, access control, etc to allow

by nijave 6y ago

imo running k8s in the cloud makes no sense. If you've already setup on prem servers, load balancers, config management, patching, access control, etc to allow developers to run applications on VMs k8s can provide an integrated experience with significantly less work. If you're running k8s in the cloud then just use a hosted service and leverage enterprise support. In the on prem case, you already have a dedicated infra team that probably has the tools to effectively deploy and manage a cluster.

pm90 6y ago
The most popular cloud product (aws) has a really shitty managed k8s offering. This is perhaps the main reason so many infra teams have spent so much collective time into building k8s. If eks was as good as GKE, what you said is absolutely spot on.
CameronNemo 6y ago
> In the on prem case, you already have a dedicated infra team that probably has the tools to effectively deploy and manage a cluster. Tools? Yes. Care and attention? Hell no. The ops team at my work still has important services running on CentOS 6, and they are spending all their time trying to get Kubernetes configured and working. You would be surprised at how much infrastructure out there is just glued together adhoc. Several senior engineers at my work are successfully blocking adoption of gitops and CD.