Get the App
SLTechnology News&Howtos  ›  Servers  › 

Kubernetes deployment (7): Node node deployment

Shulou Source: shulou.com Published: 2022-06-03 04:15:14 10月26日 Update

Related content:

Kubernetes deployment (1): architecture and function description

Kubernetes deployment (2): initialization of system environment

Kubernetes deployment (3): CA certificate making

Kubernetes deployment (4): ETCD cluster deployment

Kubernetes deployment (5): Haproxy, Keppalived deployment

Kubernetes deployment (6): Master node deployment

Kubernetes deployment (7): Node node deployment

Kubernetes deployment (8): Flannel network deployment

Kubernetes deployment (IX): CoreDNS, Dashboard, Ingress deployment

Kubernetes deployment (X): stored glusterfs and heketi deployment

Kubernetes deployment (11): managed Helm and Rancher deployment

Kubernetes deployment (12): helm deployment harbor enterprise image repository

Node only needs to install kubelet service, and all nodes need to install kube-proxy

Deploy kubelet

1. Binary package preparation

Copy the package from to all node.

[root@node-01 ~] # cd / usr/local/src/kubernetes/server/bin/ [root @ node-01 bin] # for n in `root 204206`; do scp kubelet 10.31.90.$n:/data/kubernetes/bin/; for n in [root @ node-01 bin] # for n in `root 201206`; do scp kube-proxy 10.31.90.$n:/data/kubernetes/bin/; done

two。 Create a role binding

[root@node-01] # kubectl create clusterrolebinding kubelet-bootstrap-- clusterrole=system:node-bootstrapper-- user=kubelet-bootstrapclusterrolebinding.rbac.authorization.k8s.io/kubelet-bootstrap created

3. Create a kubelet bootstrapping kubeconfig file

Set cluster parameters

[root@node-01] # kubectl config set-cluster kubernetes\-certificate-authority=/data/kubernetes/ssl/ca.pem\-embed-certs=true\-server= https://10.31.90.200:6443\-kubeconfig=bootstrap.kubeconfigCluster "kubernetes" set.

Set the client authentication parameters. Token should use the previous one.

[root@node-01] # kubectl config set-credentials kubelet-bootstrap\-token=cf25becebf64e3fffd7f3890a60ac16d\-kubeconfig=bootstrap.kubeconfig User "kubelet-bootstrap" set.

Set context parameters

[root@node-01] # kubectl config set-context default\-- cluster=kubernetes\-- user=kubelet-bootstrap\-- kubeconfig=bootstrap.kubeconfigContext "default" created.

Select the default context

[root@node-01 ~] # kubectl config use-context default-- kubeconfig=bootstrap.kubeconfigSwitched to context "default". # copy to 3 node nodes for n in `seq 204206`; do scp bootstrap.kubeconfig 10.31.90.

Deploy kubelet (node node)

Set CNI to support (all nodes) [root@node-01 ~] # mkdir-p / etc/cni/ net.d [root @ node-01 ~] # cat > > / etc/cni/net.d/10-default.conf RemoteAddress:Port Forward Weight ActiveConn InActConnTCP 10.1.0.1 Masq 443 Masq-> 10.31.90.201 Vist6443 100

If both kubelet and proxy services are installed, you can check the status using the following command:

[root@node-01] # kubectl get nodeNAME STATUS ROLES AGE VERSION10.31.90.204 Ready 40mv1.11.510.31.90.205 Ready 40mv1.11.510.31.90.206 Ready 40mv1.11.5

Please deploy the node-05,node-06 node on your own.

Follow-up will update all the installation documents one after another, if you think I wrote well, I hope you pay more attention to like, thank you very much!

Tags: Node status service certificate configuration parameter file up and down context service configuration cluster check good binary warehouse enterprise focus content function just need Apple Docker Huawei Linux macOS MariaDB Microsoft MySQL NVidia OPPO Reno Huawei OPPO Reno Shulou Information Microsoft macOS