Kubernetes configuration🔗︎
The Kubernetes section of the configuration file contains properties that are specific to Kubernetes, such as the Kubernetes version and network plugin.
Configuration🔗︎
Kubernetes manager🔗︎
v3.4.0 Default: kubespray
Specify manager that is used for deploying Kubernetes cluster. Supported values are kubespray and k3s.
kubernetes:
manager: k3s
Warning
Support for K3s manager has been added recently, therefore, it may not be fully stable.
Kubernetes version🔗︎
v3.0.0 Default: v1.28.6
By default, the Kubernetes cluster will be deployed using version v1.28.6, but you can specify a different version if necessary.
kubernetes:
version: v1.28.6
The supported Kubernetes versions include v1.28, v1.29, and v1.30.
Kubernetes network plugin🔗︎
v2.0.0 Default: calico
The calico network plugin is deployed by default in a Kubernetes cluster. However, there are multiple supported network plugins available to choose from:
calicociliumflannelkube-router
kubernetes:
networkPlugin: flannel
The following table shows the compatibility matrix of supported network plugins and Kubernetes versions:
| Kubernetes Version | Operating system | Calico | Cilium | Flannel | KubeRouter |
|---|---|---|---|---|---|
| 1.28 | Ubuntu | ||||
| 1.28 | Debian | ||||
| 1.28 | CentOS | ||||
| 1.28 | RockyLinux | ||||
| 1.29 | Ubuntu | ||||
| 1.29 | Debian | ||||
| 1.29 | CentOS | ||||
| 1.29 | RockyLinux | ||||
| 1.30 | Ubuntu | ||||
| 1.30 | Debian | ||||
| 1.30 | CentOS | ||||
| 1.30 | RockyLinux |
Note
K3s manager currently supports only flannel network plugin.
Kubernetes DNS mode🔗︎
v2.0.0 Default: coredns
Currently, the only DNS mode supported by Kubitect is coredns. Therefore, it is safe to omit this property.
kubernetes:
dnsMode: coredns
Merge kubeconfig🔗︎
v3.4.0 Default: false
Kubitect offers an option to merge the resulting Kubeconfig file with the config on path ~/.kube/config. This means that whenever a new cluster is created, it can be selected by context which equals the cluster name.
kubernetes:
other:
mergeKubeconfig: true
Auto renew control plane certificates🔗︎
v2.2.0 Default: false
Control plane certificates are renewed every time the cluster is upgraded, and their validity period is one year. However, in rare cases, clusters that are not upgraded frequently may experience issues. To address this, you can enable the automatic renewal of control plane certificates on the first Monday of each month by setting the autoRenewCertificates property to true.
kubernetes:
other:
autoRenewCertificates: true