Docs

Volcengine Kubernetes Engine

Workload FAQs

How to disable the IPv6 protocol stack in a pod

Background

When compatibility issues arise in resolving or processing IPv6 addresses within a pod due to business technology stack limitations, the IPv6 protocol stack can be disabled in the pod.

By default, pods in the cluster have the IPv6 protocol stack enabled, and their network interfaces will have the IPv6 addresses within fe80::16/64. These IPv6 addresses are automatically generated by the kernel and network protocol stack. They cannot be completely cleared by disabling either IPv6 on the node or the dual-stack feature in the cluster. This topic describes how to disable the IPv6 protocol stack in a pod manually.

Prerequisites

The vpc-cni add-on has been installed and upgraded to v1.9.6 or later.

Procedure

In the left navigation bar, click Cluster. In the right part of the page, click the target cluster name to open the management page of this cluster.

In the left navigation bar, select Configurations > ConfigMap.

In the Namespace drop-down list, select kube-system. Locate cello-config on the page, and click Update or Edit Yaml in the Actions column.

Modify the settings under 10-cello.conflist, and add the following customConfig code to disable the IPv6 protocol stack for the pod.

{
"cniVersion": "0.3.1",
"name": "cello-chainer",
"plugins": [
{
"type": "cello",
"capabilities": {
"bandwidth": true,
"com.volcengine.k8s.network-interface": true
},
"customConfig": {
"disableIPv6": true
},
"redirectToHostCIDRs": ["169.254.0.0/16"]
}
]
}

The parameter description for the customConfig field is shown in the table below.

Parameter	Type	Description
disableIPv6	Boolean	Whether to disable the IPv6 protocol stack in the Pod. Available values: true: Disable the IPv6 protocol stack in the Pod. false: Enable the IPv6 protocol stack in the Pod.

After completing the configuration, connect to the cluster via kubectl, and run the following command to perform a rolling restart of the Cello Pod so that the configuration can take effect.

kubectl rollout restart daemonset cello -n kube-system

Validating results

Deploy workloads or pods in the cluster.

Log in to the pod console, run the following command, and check whether the IPv6 protocol stack of the pod's network interface has been disabled.

ip addr

The expected result is as follows. It shows that the IPv6 protocol stack of the Pod's network interface (eth0 in this example) has been disabled.

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
link/ether 00:16:3e:2e:f1:76 brd ff:ff:ff:ff:ff:ff
inet 192.168.2.109/24 brd 192.168.2.255 scope global eth0
valid_lft forever preferred_lft forever

tip

The command to view the network interfaces varies by Linux system. This topic uses the ip addr command as an example. Note that the workloads deployed using a minimal image may not have this command installed. Refer to your actual environment.

Last updated: 2026.07.23 14:31:47