kube-proxy Mode Switch

When creating the UK8S cluster, we will generate a default kube-proxy mode for the cluster. The newly added Node nodes in the cluster will all rely on this default kube-proxy mode for addition. You can refer to the following operations to switch the kube-proxy mode of the cluster.

kube-proxy Mode Switch Operation

1. The UK8S cluster is an independent cluster you created through the {{channelName}} console. When the UK8S cluster is created, it will be created according to the kube-proxy mode you choose. Take the following cluster as an example, the cluster kube-proxy mode is default to IPVS.

2. After the creation is completed, you can modify the kube-proxy mode in the cluster overview. This modification only applies to the added nodes after the modification, and the original nodes of the cluster will not be modified. Here we change it to the iptables mode.

3. Users can see the kube-proxy mode of the node in the cluster nodes, the view of the kube-proxy mode of the cluster, if not, you can click to display this field in the settings of the page.

Note: Nodes created before December 17, 2019 have no default kube-proxy information by default.

4. To switch the kube-proxy mode of the cluster nodes, we use the operation of adding new nodes. After the new nodes are ready, delete a old node to switch all Node nodes of the cluster to the kube-proxy mode. During the switching process, the Pod of the old node will be scheduled to the new node. This operation continues until all nodes of the cluster are replaced.

Precautions

1. Please pay attention to whether your cluster is a multi-availability zone cluster. If so, it’s better to keep the newly added Node and the original Node in the same available zone.

2. If you have made an ACL policy for the IP of the Node node or have requirements for the node IP, or if you disagree with the Payment for the Node node, please do not use this plan, go to each Node node to modify the kubelet parameter. If you need to adjust the cluster’s kube-proxy mode in this way, please contact the {{channelName}} after-sales team for the operation document.

3. It is best to use a unified kube-proxy mode for the nodes of the K8S cluster. If a switch is made, please switch all Nodes in the cluster.

4. The Master node is not within the K8S scheduling range and does not need to be switched.