kubernets（k8s）init 初始化节点

admin

kubernets（k8s）init 初始化节点
7 w( P9 V: m5 p- e kubeadm init --apiserver-advertise-address=192.168.8.190 --node-name=k8s-master  --image-repository registry.aliyuncs.com/google_containers  --kubernetes-version v1.28.2 --service-cidr=192.182.22.0/20 --pod-network-cidr=192.172.21.0/20  --cri-socket=unix:///var/run/cri-dockerd.sock



建议cidir不要写太大，因为写太大会有些问题存在。比如本地的网段和规划的大网段存在冲突。
! f8 u' w* @& n" ~$ h
4 F$ g/ l: M9 w5 [7 K

admin

[root@k8s-master ~]#  kubeadm config images list
5 P. Y5 i; q: P' q, VI1229 21:16:13.799696    2756 version.go:256] remote version is much newer: v1.32.0; falling back to: stable-1.28
registry.k8s.io/kube-apiserver:v1.28.15
registry.k8s.io/kube-controller-manager:v1.28.15
! ~& f# A' u% v1 Zregistry.k8s.io/kube-scheduler:v1.28.15
registry.k8s.io/kube-proxy:v1.28.15
registry.k8s.io/pause:3.9
registry.k8s.io/etcd:3.5.9-0
. d5 o. \& [% W! U( `& @0 Yregistry.k8s.io/coredns/coredns:v1.10.1
& d6 r( a) H0 T3 Z[root@k8s-master ~]#  kubeadm init --apiserver-advertise-address=192.168.8.190 --node-name=k8s-master  --image-repository registry.aliyuncs.com/google_containers  --kubernetes-version v1.28.2 --service-cidr=192.182.22.0/20 --pod-network-cidr=192.172.21.0/20  --cri-socket=unix:///var/run/cri-dockerd.sock
[init] Using Kubernetes version: v1.28.2
: @3 ~& j' d% p3 J; L, A[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
* Y) {, ~- j4 {* w7 e[preflight] This might take a minute or two, depending on the speed of your internet connection
, C& I- w. Y  w3 F( }[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
: l" Q* U& `, S5 G5 z[certs] Using certificateDir folder "/etc/kubernetes/pki"
[certs] Generating "ca" certificate and key
8 R  X7 Y: T+ V3 A4 b: @5 H[certs] Generating "apiserver" certificate and key
[certs] apiserver serving cert is signed for DNS names [k8s-master kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [192.182.16.1 192.168.8.190]
! K0 `# W% b5 N$ U: j[certs] Generating "apiserver-kubelet-client" certificate and key
[certs] Generating "front-proxy-ca" certificate and key
  A8 z/ i( z. A' T" t8 i[certs] Generating "front-proxy-client" certificate and key
[certs] Generating "etcd/ca" certificate and key
  Q" t! I) R$ f. N+ E$ Y1 h[certs] Generating "etcd/server" certificate and key
- l! b! E( ]9 K7 I3 `[certs] etcd/server serving cert is signed for DNS names [k8s-master localhost] and IPs [192.168.8.190 127.0.0.1 ::1]
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [k8s-master localhost] and IPs [192.168.8.190 127.0.0.1 ::1]
[certs] Generating "etcd/healthcheck-client" certificate and key
: V4 p# Z# B4 G$ Y8 i+ z! ?[certs] Generating "apiserver-etcd-client" certificate and key
7 s8 G) L5 [( C[certs] Generating "sa" key and public key
8 |$ e# v4 n6 F) }7 j4 l[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
5 I2 _8 x( v1 p: `1 f! s[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
3 T! h0 i: \7 m2 j0 p* y+ n" y[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
( d. b6 A5 g% y, Y[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
: }, Q4 ^! }- S% R# e* m[control-plane] Creating static Pod manifest for "kube-controller-manager"
: N( s3 K" |& x! x2 u3 F) Z8 p[control-plane] Creating static Pod manifest for "kube-scheduler"
+ w: O" M( |: R9 ^" g& C0 ][kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
7 f% A9 i* |% p. F$ [[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
% ~! X& ]( D& w. x[kubelet-start] Starting the kubelet
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
4 e+ Y" m2 G( c$ E3 ?7 v[apiclient] All control plane components are healthy after 10.503849 seconds
[upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
/ x1 x! X$ [- S5 Z, F[kubelet] Creating a ConfigMap "kubelet-config" in namespace kube-system with the configuration for the kubelets in the cluster
[upload-certs] Skipping phase. Please see --upload-certs
5 e! g' l1 k) u9 m+ q! Z[mark-control-plane] Marking the node k8s-master as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]
[mark-control-plane] Marking the node k8s-master as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]
: Z4 Z8 T/ C$ O: |" |( t[bootstrap-token] Using token: gz21hk.okzfsa63qkqquxwr
6 {' S: }& U' }2 o8 r$ N[bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles
% V& K% \: C  O) ?[bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes
4 e; z1 U6 [5 y& U2 N. q& m5 y/ _[bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials
8 O( `* N7 n. q; r7 b[bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
[bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
[bootstrap-token] Creating the "cluster-info" ConfigMap in the "kube-public" namespace
+ v* g) f% H4 m* R0 Y* [[kubelet-finalize] Updating "/etc/kubernetes/kubelet.conf" to point to a rotatable kubelet client certificate and key
[addons] Applied essential addon: CoreDNS
[addons] Applied essential addon: kube-proxy
% j* C5 P) Y5 U  i; C$ z
Your Kubernetes control-plane has initialized successfully!

To start using your cluster, you need to run the following as a regular user:
, k0 X. J0 A6 N8 ~* W/ H! M8 d8 q6 \
  mkdir -p $HOME/.kube
5 J5 B: {0 }" j  sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
; ?. R+ `  c4 g/ k9 {# ~  sudo chown $(id -u):$(id -g) $HOME/.kube/config

& `) h7 k+ A: X- ]4 cAlternatively, if you are the root user, you can run:

5 i1 ^9 V9 J, E+ t& }6 n5 W' H- x  export KUBECONFIG=/etc/kubernetes/admin.conf
( O( e- A0 @+ j7 x" _
You should now deploy a pod network to the cluster.
# S3 b6 y, S9 f9 _9 g. `Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
  https://kubernetes.io/docs/conce ... inistration/addons/

Then you can join any number of worker nodes by running the following on each as root:

' q; o( h3 b0 q7 C0 T4 wkubeadm join 192.168.8.190:6443 --token gz21hk.okzfsa63qkqquxwr \
! k0 Q9 R$ v0 j' Z        --discovery-token-ca-cert-hash sha256:5aeba3bb6d94b76440997cbc4ee9c2ef8a791211a7da0abb39a75142a040bc00