How does managed kubernetes providers hide the control plane?

• kubernetes-the-hard-way

  126 38,532 0.0

  Bootstrap Kubernetes the hard way. No scripts.

But if you boil down a control plane to its most essential components, it is basically a database (etcd), a webservice (apiserver) and two controllers (controler-manager, scheduler), none of which requires a Kubernetes cluster for their own needs. Self-hosting the control-plane the kubeadm way is absolutely not a requirement, you can also download the bare binaries and run them as basic systemd units out of the cluster. This is how the Kubernetes the hard way tutorial makes things work, if you want to have a look.

• gardener

  9 2,740 9.9 Go

  Kubernetes-native system managing the full lifecycle of conformant Kubernetes clusters as a service on Alicloud, AWS, Azure, GCP, OpenStack, vSphere, KubeVirt, Hetzner, EquinixMetal, MetalStack, and OnMetal with minimal TCO.

  

Now, if you want to dig further on how cloud providers operate, like I said, most are actually using Kubernetes to automate the client control plane management. There is a cloud-neutral project for this out there called Gardener, they have a few architecture documents which explain the concept a bit further. In their garden metaphor, the seed cluster hosts the client control planes, and the shoot clusters are the client clusters (which are only made of worker nodes, no control-plane node). Another more specialized implementation is Kubernikus for OpenStack.

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• kubernikus

  1 135 8.7 Go

  Kubernetes as a Service for Openstack

  

Now, if you want to dig further on how cloud providers operate, like I said, most are actually using Kubernetes to automate the client control plane management. There is a cloud-neutral project for this out there called Gardener, they have a few architecture documents which explain the concept a bit further. In their garden metaphor, the seed cluster hosts the client control planes, and the shoot clusters are the client clusters (which are only made of worker nodes, no control-plane node). Another more specialized implementation is Kubernikus for OpenStack.

Suggest a related project