Pod IP Pools
A Pod IP pool is used to manage the Pod network address space, and the address space between each Pod IP pool cannot overlap. When you create a workload, you can select a specific Pod IP pool, so that created Pods will be assigned IP addresses from this Pod IP pool.
Enable Pod IP Pools Before Installation
Installing on Linux
When you implement multi-node installation of KubeSphere on Linux, you need to create a configuration file, which lists all KubeSphere components.
In the tutorial of Installing KubeSphere on Linux, you create a default file
config-sample.yaml
. Modify the file by executing the following command:vi config-sample.yaml
Note
If you adopt All-in-One Installation, you do not need to create aconfig-sample.yaml
file as you can create a cluster directly. Generally, the all-in-one mode is for users who are new to KubeSphere and look to get familiar with the system. If you want to enable Pod IP Pools in this mode (for example, for testing purposes), refer to the following section to see how Pod IP pools can be installed after installation.In this file, navigate to
network.ippool.type
and changenone
tocalico
. Save the file after you finish.network: ippool: type: calico # Change "none" to "calico".
Create a cluster using the configuration file:
./kk create cluster -f config-sample.yaml
Installing on Kubernetes
As you install KubeSphere on Kubernetes, you can enable Pod IP Pools first in the cluster-configuration.yaml file.
Download the file cluster-configuration.yaml and edit it.
vi cluster-configuration.yaml
In this local
cluster-configuration.yaml
file, navigate tonetwork.ippool.type
and enable it by changingnone
tocalico
. Save the file after you finish.network: ippool: type: calico # Change "none" to "calico".
Execute the following commands to start installation:
kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3.4.1/kubesphere-installer.yaml kubectl apply -f cluster-configuration.yaml
Enable Pod IP Pools After Installation
Log in to the console as
admin
. Click Platform in the upper-left corner and select Cluster Management.Click CRDs and enter
clusterconfiguration
in the search bar. Click the result to view its detail page.Info
A Custom Resource Definition (CRD) allows users to create a new type of resources without adding another API server. They can use these resources like any other native Kubernetes objects.In Custom Resources, click on the right of
ks-installer
and select Edit YAML.In this YAML file, navigate to
network
and changenetwork.ippool.type
tocalico
. After you finish, click OK in the lower-right corner to save the configuration.network: ippool: type: calico # Change "none" to "calico".
You can use the web kubectl to check the installation process by executing the following command:
kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l 'app in (ks-install, ks-installer)' -o jsonpath='{.items[0].metadata.name}') -f
Note
You can find the web kubectl tool by clicking in the lower-right corner of the console.
Verify the Installation of the Component
On the Cluster Management page, verify that you can see the Pod IP Pools module under Network.
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.