大网数据广告活动
服务器运维问答

What is the point of running self managed kubernetes cluster?

· 52CE 我爱测

I have been researching k8s lately. I am a bit confused by the idea of self managing k8s cluster in the cloud. I have read about people doing it, but still I am not sure what are the price benefits if you are already running serv…

问题原文

原帖链接 · hahcho · CC BY-SA 4.0

I have been researching k8s lately. I am a bit confused by the idea of self managing k8s cluster in the cloud. I have read about people doing it, but still I am not sure what are the price benefits if you are already running services on VMs in the cloud.

GKE makes you pay only for your nodes and it manages your master nodes out of the box.

Are there some hidden costs for the managed clusters that are not mentioned? Will you self manage your cluster if you are already running services in the cloud and you will most probably pay the same if you migrate them in k8s?

I know it really depends based on your services and needs but lets imagine the most basic CRUD application - 1 stateless backend running a few replicas, 1 stateful db running one replica for HA purposes, 1 message broker and a few worker instances for background processing. You do not have bare metal machines, you are already running in the cloud on basic VMs, without containers. Will there be any good reason to migrate to self managed k8s cluster price wise?

已采纳解答

原帖链接 · Mark Watney · CC BY-SA 4.0

By using a Self-Managed Kubernetes Cluster you have many pros and cons.

As a pro, on a self-managed Kubernetes Cluster, you have control over the management layer. Fully managed Kubernetes services in the cloud don’t allow you to configure the cluster master, because that component is handled by the managed service. When you deploy your own cluster using kubeadm, kubespray or even doing it the hard way, you have full access to the cluster master all the other related management components.

This also adds flexibility of configuration where you can configure the cluster and the nodes the way you want, instead of wrestling with the configuration options supported by a managed service.

You also have more control over the deployment and management of your cluster. For example, you can deploy multiple node pools or choose to have different instance types for different nodes. These options aren’t available with many managed Kubernetes services.

On the other hand, you have the fact that deploying and maintain a self-managed cluster is time-consuming and requires deeper knowledge from the maintainer. Cloud providers have specific teams to take care of these solutions and in general, this adds more reliability to the solutions provided.

There are more pros and cons described in this article. It's from NetApp but part of the post is not specific to it and it worth reading it.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2019-11-25)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。