...
...
...
...
...
...
...
...
...
...
...
...
...
This page will go through the requirements for a Kubernetes installer based on RA-2.
It differs from the existing comparison of installers, as Kubeadm has been removed. Some of the remaining installers still utilize Kubeadm as a bootstrapping tool, but it will not be considered as an installer by itself.
...
The chosen runtime must be conformant with the Kubernetes Container Runtime Interface (CRI) and the Open Container Initiative (OCI) runtime spec.
Reference: TBD (below content is based on the High Level Architecture)
| Feature | Airship | Kind | KubeOne | Kubespray | OpenShift Origin (OKD) |
|---|---|---|---|---|---|
| Container Runtime | Docker | Docker | Docker | Docker | Docker |
...
Align with the Kubernetes version support policy
Reference: ra2.k8s.005
The version support policy states that the most recent 3 minor releases (n-2) are supported. The reference implementation, and therefore the Kubernetes installer, must align with this policy.
...
The features are:
- CPU Manager (Beta) - ra2.k8s.006
- Topology Manager (Beta) - ra2.k8s.006
- Device Plugin (Beta) - ra2.k8s.007
- IPv6 Dual Stack Feature - ra2.k8s.010
As of Kubernetes v1.18, all features are in "Beta" state and enabled by default. Prior to this, Topology Manager has been in "Alpha" state, and had to be enabled through a Kubelet feature-gates.
...
The CNI Plugin chosen by the installer should be compliant with the default Kubernetes networking assumptions.