Prerequisites for Self-Managed Node Creation
Find out the prerequisites for creating self-managed nodes.
Before you create a self-managed node and add it to a cluster:
- Confirm the cluster to which you want to add a self-managed node is configured appropriately (see Cluster Requirements).
- Make sure you select an appropriate image for the compute instance hosting the self-managed node (see Image Requirements).
Cluster Requirements
The cluster to which you add a self-managed node must be an enhanced cluster.
The cluster's control plane nodes must be running Kubernetes version 1.25 (or later). To use the OCI VCN-Native Pod Networking CNI plugin for pod networking (instead of the flannel CNI plugin), the cluster's control plane nodes must be running Kubernetes version 1.27.10 (or later).
Bear in mind that the versions of Kubernetes running on control plane nodes and on worker nodes (including self-managed nodes) must be compatible, as described in the Kubernetes version skew support policy in the Kubernetes documentation. That is, the Kubernetes version on control plane nodes must be no more than two minor versions (or three minor versions, starting from Kubernetes version 1.28) ahead of the Kubernetes version on worker nodes . See Image Requirements.
Image Requirements
The image you specify for a self-managed node must be one of the OKE Oracle Linux 7 (OL7) or Oracle Linux 8 (OL8) images, and the image must have a Release Date of March 28, 2023 or later.
Obtain the image OCID from OKE Worker Node Oracle Linux 7.x Images and OKE Worker Node Oracle Linux 8.x Images.
Note that when creating a self-managed node, it is your responsibility to specify an image containing a Kubernetes version that complies with the Kubernetes version skew support policy described in the Kubernetes documentation. Kubernetes Engine does not check that the Kubernetes version in the image you specify for a self-managed node is compatible with the Kubernetes version running on the cluster's control plane nodes. See Cluster Requirements.