In a typical Kubernetes cluster, several containers located in different pods need to communicate with other containers within the same pods for performance and fault tolerance reasons. When developing and deploying applications, the IP addresses of these containers are unknown in advance. For instance, an application server may need to connect to a MariaDB instance, but the MariaDB's IP will vary for each pod.
The primary role of kube-proxy is to manage Kubernetes services. When an application needs to connect to MariaDB, it connects to the MariaDB service instead.
kube-proxy then receives the request and redirects it to a running MariaDB container within the same pod.
Kubernetes orchestrates containers within a pod using a container runtime that complies with the Kubernetes Container Runtime Interface (CRI). Approved container runtimes are detailed on the Container Runtimes page of the Kubernetes documentation. Additional details about the CRI can be found on GitHub.
Initially, Kubernetes defaulted to using Docker as its container runtime. Though now deprecated, Docker images remain viable with any compatible container runtime.
| ### Controllers Controllers constantly check if there are differences between the pod's current state and their desired state. When differences are found, controllers try to fix them. Each node type controls one or more resource types. Several types of controllers are needed to run a cluster. Most of the actions taken by the controllers user the API server in the Control Plane. However, this is not necessarily true for custom controllers. Also, some actions cannot be performed via the Control Plane. For example, if some nodes crashed, adding new nodes involves taking actions outside of the Kubernetes cluster, and controllers will have to do this themselves. It is possible to write custom controllers to perform checks that require knowledge about a specific technology. For example, a MariaDB custom controller may want to check if [replication](/docs/server/ha-and-performance/standard-replication.md) is working by issuing [SHOW REPLICA STATUS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-replica-status.md) commands. This logic is specific to the way MariaDB works, and can only be implemented in a customer controller. Custom controllers are usually part of operators. For more information, see [Controllers](https://kubernetes.io/docs/concepts/architecture/controller/) in the Kubernetes documentation. ### Control Plane The control plane consists of the following components. For more information about the control plane, see [Control Plane Components](https://kubernetes.io/docs/concepts/overview/components/) in Kubernetes documentation. #### API Server An API Server exposes API functions both internally and externally. It is essential to coordinate Kubernetes components so that they react to node's change of state, and it allows the user to send commands. The default implementation of the API Server is kube-apiserver. It is able to scale horizontally and to balance the load between its instances. | Component | Description | | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `kube-controller-manager` | Most controllers run in this component. | | `etcd` | Contains all data used by a Kubernetes cluster. Taking regular backups of etcd data is advisable. | | `kube-scheduler` | Decides which node should host a new pod based on criteria like resource requirements. | | `cloud-controller-manager` | Implements logic and API of a cloud provider. Handles requests from the API Server and performs actions specific to a cloud vendor, like creating instances. | ### Clients and Tools Kubernetes comes with a set of tools that allow us to communicate with the API server and test a cluster. | Tool | Description | | ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `kubectl` | Enables communication with the API server and allows running commands on a Kubernetes cluster. | | `kubeadm` | Facilitates the creation of a Kubernetes cluster ready to receive commands from kubectl. | | `kind` | Used to create and manage test clusters on a personal machine. It creates a cluster consisting of Docker containers, requiring Docker to be installed. Available on Linux, MacOS, and Windows. | | `minikube` | Runs a single-node cluster on the local machine. Available on Linux, MacOS, and Windows. | ## Kubernetes Resources and References * [Kubernetes website](https://kubernetes.io/). * [Kubernetes](https://en.wikipedia.org/wiki/Kubernetes) on Wikipedia. * [Kubernetes organization](https://github.com/kubernetes) on GitHub. * [The Official MariaDB Operator](https://github.com/mariadb-operator/mariadb-operator) * [OperatorHub.io](https://operatorhub.io/) * [Kubernetes Community Forums](https://discuss.kubernetes.io/). * (video) [MariaDB database clusters on Kubernetes](https://mariadb.org/fest2020/kubernetes/), by Pengfei Ma, at MariaDB Server Fest 2020. * Series of posts by Anel Husakovic on the MariaDB Foundation blog: * [Start MariaDB in K8s](https://mariadb.org/start-mariadb-in-k8s/) * [MariaDB & K8s: Communication between containers/Deployments](https://mariadb.org/mariadb-k8s-communication-between-containers-deployments/) * [MariaDB & K8s: Create a Secret and use it in MariaDB deployment](https://mariadb.org/mariadb-k8s-create-a-secret-and-use-it-in-mariadb-deployment/) * [MariaDB & K8s: Deploy MariaDB and WordPress using Persistent Volumes](https://mariadb.org/mariadb-k8s-deploy-mariadb-and-wordpress-using-persistent-volumes/) * [Create statefulset MariaDB application in K8s](https://mariadb.org/create-statefulset-mariadb-application-in-k8s/) * [MariaDB replication using containers](https://mariadb.org/mariadb-replication-using-containers/) * [MariaDB & K8s: How to replicate MariaDB in K8s](https://mariadb.org/mariadb-k8s-how-to-replicate-mariadb-in-k8s/) Content initially contributed by [Vettabase Ltd](https://vettabase.com/). *This page is licensed: CC BY-SA / Gnu FDL* {% @marketo/form formId="4316" %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://mariadb.com/docs/server/server-management/automated-mariadb-deployment-and-administration/kubernetes-and-mariadb/kubernetes-overview-for-mariadb-users.md?ask=