매주 한 page, 기술 한 spoon

---
apiVersion: kubeadm.k8s.io/v1beta3
kind: ClusterConfiguration
clusterName: kubernetes
etcd:
  local:
    dataDir: /var/lib/etcd
networking:
  dnsDomain: cluster.local
  serviceSubnet: 10.96.0.0/12
  podSubnet: 10.244.0.0/16
kubernetesVersion: v1.23.17
certificatesDir: /etc/kubernetes/pki
controlPlaneEndpoint: "192.168.0.20:6443"
apiServer:
  extraArgs:
    authorization-mode: Node,RBAC
  certSANs:
    - "127.0.0.1"
    - "192.168.0.21"
    - "192.168.0.22"
    - "192.168.0.23"
    - "192.168.0.20"
controllerManager: {}
scheduler: {}

sudo kubeadm init --config=./kubeadm-init.yml --upload-certs

root@ubuntu:~# ls -l /etc/kubernetes/manifests/
total 20
-rw------- 1 root root 2270 May  4 07:40 etcd.yaml
-rw------- 1 root root 4015 May  4 07:40 kube-apiserver.yaml
-rw------- 1 root root 3521 May  4 07:40 kube-controller-manager.yaml
-rw------- 1 root root 1441 May  4 07:40 kube-scheduler.yaml
-rw-r--r-- 1 root root 1454 May  4 07:40 kube-vip.yml

[bootstrap-token] Creating the "cluster-info" ConfigMap in the "kube-public" namespace
[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

Your Kubernetes control-plane has initialized successfully!

To start using your cluster, you need to run the following as a regular user:

  mkdir -p $HOME/.kube
  sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
  sudo chown $(id -u):$(id -g) $HOME/.kube/config

Alternatively, if you are the root user, you can run:

  export KUBECONFIG=/etc/kubernetes/admin.conf

You should now deploy a pod network to the cluster.
Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
  https://kubernetes.io/docs/concepts/cluster-administration/addons/

You can now join any number of the control-plane node running the following command on each as root:

  kubeadm join 192.168.0.200:6443 --token qt949j.5t8cdmxstjeann38 \
        --discovery-token-ca-cert-hash sha256:9401439393b2ad6da3ae5120eb77bd40953bd33feb586de2028d59a94f407bda \
        --control-plane --certificate-key 9a6376814a696f6d1de5a736f9b99adf865042ffe33ea58f810ee3282d47291c

Please note that the certificate-key gives access to cluster sensitive data, keep it secret!
As a safeguard, uploaded-certs will be deleted in two hours; If necessary, you can use
"kubeadm init phase upload-certs --upload-certs" to reload certs afterward.

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

kubeadm join 192.168.0.200:6443 --token qt949j.5t8cdmxstjeann38 \
        --discovery-token-ca-cert-hash sha256:9401439393b2ad6da3ae5120eb77bd40953bd33feb586de2028d59a94f407bda

kubeadm join 192.168.0.200:6443 --token qt949j.5t8cdmxstjeann38 \
        --discovery-token-ca-cert-hash sha256:9401439393b2ad6da3ae5120eb77bd40953bd33feb586de2028d59a94f407bda \
        --control-plane --certificate-key 9a6376814a696f6d1de5a736f9b99adf865042ffe33ea58f810ee3282d47291c

[certs] Generating "front-proxy-client" certificate and key
[certs] Valid certificates and keys now exist in "/etc/kubernetes/pki"
[certs] Using the existing "sa" key
[kubeconfig] Generating kubeconfig files
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[check-etcd] Checking that the etcd cluster is healthy
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Starting the kubelet
[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
[etcd] Announced new etcd member joining to the existing etcd cluster
[etcd] Creating static Pod manifest for "etcd"
[etcd] Waiting for the new etcd member to join the cluster. This can take up to 40s
The 'update-status' phase is deprecated and will be removed in a future release. Currently it performs no operation
[mark-control-plane] Marking the node worker1 as control-plane by adding the labels: [node-role.kubernetes.io/master(deprecated) node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]
[mark-control-plane] Marking the node worker1 as control-plane by adding the taints [node-role.kubernetes.io/master:NoSchedule]

This node has joined the cluster and a new control plane instance was created:

* Certificate signing request was sent to apiserver and approval was received.
* The Kubelet was informed of the new secure connection details.
* Control plane (master) label and taint were applied to the new node.
* The Kubernetes control plane instances scaled up.
* A new etcd member was added to the local/stacked etcd cluster.

To start administering your cluster from this node, you need to run the following as a regular user:

        mkdir -p $HOME/.kube
        sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
        sudo chown $(id -u):$(id -g) $HOME/.kube/config

Run 'kubectl get nodes' to see this node join the cluster.

root@ubuntu:~#
root@ubuntu:~#   mkdir -p $HOME/.kube
root@ubuntu:~#   sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
root@ubuntu:~#   sudo chown $(id -u):$(id -g) $HOME/.kube/config
root@ubuntu:~# kubectl get node
NAME      STATUS     ROLES                  AGE     VERSION
master1   NotReady   control-plane,master   8m32s   v1.23.17
worker1   NotReady   control-plane,master   3m40s   v1.23.17
worker2   NotReady   control-plane,master   12s     v1.23.17