: firewalld is active, please ensure ports are open or your cluster may not function correctly This is the output of my initialization command. You can choose to pass the socket file to the runtime and publish the address according to your settings. Note: If 192.168.0.0/16 is already used in your network, you must select another Pod network CIDR to replace 192.168.0.0/16 in the above command.Ĭontainer runtime socket: Unix domain socket RuntimePath Set the DNS name of the cluster endpoint or add records to the /etc/hosts file. apiserver-advertise-address : Set advertise address for this particular control-plane node's API server cri-socket : Use if have more than one container runtime to set runtime socket path pod-network-cidr : Used to set a Pod network add-on CIDR
control-plane-endpoint : set the shared endpoint for all control-plane nodes.
These are basic kubeadm init Options for booting the cluster. Pull the container image: $ sudo kubeadm config images pull Now, we want to initialize the computer that will run the control plane components (including etcd (cluster database) and API server). Log in to the server used as the main server and ensure that the br_netfilter module is loaded: $ lsmod | grep br_netfilterīridge 151336 2 br_netfilter,ebtable_brouteĮnable kubelet service. Sudo firewall-cmd -reload Step 6: Initialize your control plane nodes Main server port: sudo firewall-cmd -add-port=/udp -permanent If you have an active firewall service, you need to enable multiple ports.
#Kubeadm centos driver
When using kubeadm, please configure manually kubelet's cgroup driver Step 5: Configure the firewall To use the systemd cgroup driver, set _cgroup = true In /etc/containerd/config.toml. Sudo tee /etc/modules-load.d/nf < /etc/containerd/config.toml # Configure persistent loading of modules
0 kommentar(er)
