Observe the cluster status at the control node The output of this operation is as follows: # kubectl apply -f flannel/Documentation/kube-flannel.yml # kubectl apply -f flannel/Documentation/kube-flannel-rbac.yml This reflects services as defined in the Kubernetes API on each node and can do simple TCP, UDP, and SCTP stream forwarding or round robin TCP, UDP, and SCTP forwarding across a set of backends. Kubeadm join -token 192.168.120.122:6443įollow the prompt for the initialization command: Synopsis The Kubernetes network proxy runs on each node. You can now join any number of machines by running the following on each node as root: yaml" with one of the options listed at: You should now deploy a pod network to the cluster. To start using your cluster, you need to run (as a regular user): Your Kubernetes master has initialized successfully! The result is that kube-proxy’s connection processing in. This works, it also uses a mature kernel feature and IPVS is designed for load balancing lots of services it has an optimized API and an optimized look-up routine rather than a list of sequential rules. First node has registered after 6.039626 seconds In IPVS mode, kube-proxy programs the IPVS load balancer instead of using iptables. Waiting for at least one node to register All control plane components are healthy after 1377.560339 seconds Created API client, waiting for the control plane to become ready Wrote KubeConfig file to disk: "/etc/kubernetes/nf" Valid certificates and keys now exist in "/etc/kubernetes/pki" Generated front-proxy client certificate and key. Generated front-proxy CA certificate and key. Generated service account token signing key and public key. Generated API server kubelet client certificate and key. API Server serving cert is signed for DNS names and IPs Generated API server certificate and key. WARNING: kubeadm is in beta, please do not use it for production clusters. The output of this command is as follows:
Through the NAT mode of ipvs, the virtual IP to the POD IP is forwarded for the request to access the k8s service. In kubernetes version 1.8 or higher, the kube-proxy component has added support for ipvs mode in addition to iptables mode and user mode. Note: Initialization is slow because the process will pull1 some docker image. Kubeadm simplifies the deployment process by containerizing Kubernetes-related services. The pod-ES65en-ES66en parameter must be added because flannel will be used to build the pod network in this cluster. # systemctl enable kubelet & systemctl start kubelet # systemctl enable docker & systemctl start docker
#Kubeadm centos 7 kube proxy ipvs install#
# yum install -y docker kubelet kubeadm kubectl kubernetes-cni Install the following packages on all nodes: # sed -i.bak 's/SELINUX=enforcing/SELINUX=permissive/' /etc/selinux/config # systemctl stop rvice & systemctl disable rvice The packages used for this deployment are provided by google associated sources, so the cluster nodes must be able to access the extranet, which you can configure yourself.
That is, the cluster contains 1 control node and 3 working nodes.Ĭonfiguration can be accessed on the google web site This article refers to the Installing Kubernetes Linux with kubeadm article on kubernetes Installing Kubernetes Linux kubeadm using Kubeadm to deploy Kuebernetes clusters in ES8en 7.2, which solves 1 of the problems encountered when deploying in accordance with this document.
0 kommentar(er)
