Disable and Enable Pod IP Pools
This section introduces how to disable and enable pod IP pools.
After a pod IP pool is disabled, it will not continue to allocate IP addresses and will not affect the network of pods that have already been allocated IP addresses. However, disabling a pod IP pool will automatically unbind its associated projects. When migrating a pod IP pool, the number of available addresses in the new IP pool must not be less than the number of IP addresses used in the current IP pool.
Warning |
---|
After migration, workloads will be restarted. Please proceed with caution. |
Prerequisites
You should join a cluster and have the Cluster Network Resource Management permission within the cluster. For more information, refer to "Cluster Members" and "Cluster Roles".
KubeSphere Network should have been installed and enabled.
Steps
Log in to the KubeSphere web console with a user who has the Cluster Network Resource Management permission, and access your cluster.
Click Network > Pod IP Pools in the left navigation pane.
Click on the right side of the pod IP pool you want to operate, and then select Disable from the dropdown list.
In the Disable Pod IP Pool dialog box, click OK.
Click on the right side of the disabled pod IP pool, and then select Enable from the dropdown list to enable the pod IP pool.
If there are allocated IPs in the disabled pod IP pool, check Migrate Pod IP Pool to migrate the pods with allocated IP addresses to a new pod IP pool.
Feedback
Was this page Helpful?
Receive the latest news, articles and updates from KubeSphere
Thanks for the feedback. If you have a specific question about how to use KubeSphere, ask it on Slack. Open an issue in the GitHub repo if you want to report a problem or suggest an improvement.