Managed components
centron Kubernetes takes care of the operation of the cluster infrastructure for you. This page lists which components centron manages, which are included in the delivery, and where your responsibilities begin.
Managed by centron
Control Plane
The entire control plane is operated, monitored and updated by centron:
- kube-apiserver – Endpoint for all Kubernetes API requests
- etcd – The cluster’s state store
- kube-scheduler – Deployment of pods onto nodes
- kube-controller-manager – Reconciliation of actual and target states
Direct access to these components is not provided. They interact exclusively via the Kubernetes API.
Node operating system and Kubernetes components
The operating system, kubelet and container runtime on the worker nodes are maintained via automatic upgrades. Minor patches and critical security updates are installed by centron on a rolling basis within the configured upgrade window – node by node and without any downtime.
Cluster network
The Container Network Interface (CNI) and the pod and service networks are set up and managed by centron. The address ranges are defined when the cluster is created.
Cluster Autoscaler
The Cluster Autoscaler is part of the managed environment. You enable it for each node pool and specify the minimum and maximum number of nodes; centron handles its operation.
Integrated features included
These components are pre-installed or integrated and are available to you without the need for separate installation:
| Component | Function |
|---|---|
| centron Metrics Agent | Pre-installed on all worker nodes. Provides CPU, memory, disk I/O and bandwidth data for the Analytics tab. |
| CoreDNS | Intra-cluster name resolution. |
Currently unavailable
Two integrations that are often required in managed Kubernetes environments are currently not available:
| Component | Impact |
|---|---|
| Cloud Controller Manager (CCM) | Services of type LoadBalancer do not receive an external address and remain at EXTERNAL-IP: <pending>. Use NodePort instead. |
The Storage Features and Deploying the First Image sections describe how to do this.
Your responsibility
centron manages the cluster infrastructure – you are responsible for everything that runs within the cluster:
- Workloads: Deployments, StatefulSets, Jobs, manifests and container images
- Cluster configuration: Namespaces, RBAC rules, network policies, secrets and ConfigMaps
- Additional components: Ingress controllers, service meshes, monitoring stacks and other self-installed software
- Sizing: Selection of instance types and the number of nodes per pool
- Data backup: Backing up your application data and persistent volumes
- Resource requirements: Appropriate
requestsandlimitssettings for your pods
An Ingress Controller is not pre-installed. To access HTTP services externally, you will need to install an Ingress Controller yourself; see Installing an Ingress Controller.