Kubernetes で Minecraft Server を設置する（その１）

cat <<EOF | sudo tee /etc/modules-load.d/k8s.conf
overlay
br_netfilter
EOF

sudo modprobe overlay
sudo modprobe br_netfilter

cat <<EOF | sudo tee /etc/sysctl.d/k8s.conf
net.bridge.bridge-nf-call-iptables  = 1
net.bridge.bridge-nf-call-ip6tables = 1
net.ipv4.ip_forward                 = 1
EOF

sudo sysctl --system

lsmod | grep br_netfilter
br_netfilter           32768  0
bridge                409600  1 br_netfilter

lsmod | grep overlay
overlay               188416  0

sysctl net.bridge.bridge-nf-call-iptables net.bridge.bridge-nf-call-ip6tables net.ipv4.ip_forward
net.bridge.bridge-nf-call-iptables = 1
net.bridge.bridge-nf-call-ip6tables = 1
net.ipv4.ip_forward = 1

※一時的に無効化
swapoff -a

※続いて永続的に無効化
vi /etc/fstab

次の行をコメントアウト
# /swap.img     none    swap    sw      0       0

※再マウント
sudo mount -a

127.0.0.1 localhost
127.0.1.1 k8s-node1

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

# 以下を追記
10.1.1.3 k8s-node1
10.1.1.6 k8s-node4
10.1.1.7 k8s-node5
10.1.1.8 k8s-node6

sudo su

export VERSION=1.28
export OS=xUbuntu_22.04

echo "deb [signed-by=/usr/share/keyrings/libcontainers-archive-keyring.gpg] https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/$OS/ /" > /etc/apt/sources.list.d/devel:kubic:libcontainers:stable.list
echo "deb [signed-by=/usr/share/keyrings/libcontainers-crio-archive-keyring.gpg] https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/$VERSION/$OS/ /" > /etc/apt/sources.list.d/devel:kubic:libcontainers:stable:cri-o:$VERSION.list

mkdir -p /usr/share/keyrings
curl -L https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/$OS/Release.key | gpg --dearmor -o /usr/share/keyrings/libcontainers-archive-keyring.gpg
curl -L https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/$VERSION/$OS/Release.key | gpg --dearmor -o /usr/share/keyrings/libcontainers-crio-archive-keyring.gpg

apt-get update
apt-get install cri-o cri-o-runc

systemctl daemon-reload
systemctl start crio
systemctl enable crio

sudo apt-get update
sudo apt-get install -y apt-transport-https ca-certificates curl gpg

curl -fsSL https://pkgs.k8s.io/core:/stable:/v1.28/deb/Release.key | sudo gpg --dearmor -o /etc/apt/keyrings/kubernetes-apt-keyring.gpg

echo 'deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] https://pkgs.k8s.io/core:/stable:/v1.28/deb/ /' | sudo tee /etc/apt/sources.list.d/kubernetes.list

sudo apt-get update
sudo apt-get install -y kubelet kubeadm kubectl

# バージョンを固定するため、パッケージが更新されないようにする。
sudo apt-mark hold kubelet kubeadm kubectl

sudo crictl info

{
  "status": {
    "conditions": [
      {
        "type": "RuntimeReady",
        "status": true,
        "reason": "",
        "message": ""
      },
      {
        "type": "NetworkReady",
        "status": true,
        "reason": "",
        "message": ""
      }
    ]
  },
  "config": {
    "sandboxImage": "registry.k8s.io/pause:3.9"
  }
}

sudo kubeadm init --control-plane-endpoint 10.1.1.3 --pod-network-cidr=10.244.0.0/16

The reset process does not clean CNI configuration. To do so, you must remove /etc/cni/net.d

The reset process does not reset or clean up iptables rules or IPVS tables.
If you wish to reset iptables, you must do so manually by using the "iptables" command.

If your cluster was setup to utilize IPVS, run ipvsadm --clear (or similar)
to reset your system's IPVS tables.

The reset process does not clean your kubeconfig files and you must remove them manually.
Please, check the contents of the $HOME/.kube/config file.

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

sudo kubeadm join 10.1.1.3:6443 --token upnaaa.pk・・・・・25 --discovery-token-ca-cert-hash sha256:e1・・・・・00

[preflight] Running pre-flight checks
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
[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...

This node has joined the cluster:
* Certificate signing request was sent to apiserver and a response was received.
* The Kubelet was informed of the new secure connection details.

Run 'kubectl get nodes' on the control-plane to see this node join the cluster.

kubectl get nodes

NAME        STATUS   ROLES           AGE   VERSION
k8s-node1   Ready    control-plane   43m    v1.28.3
k8s-node4   Ready    <none>          20m    v1.28.3
k8s-node5   Ready    <none>          2m8s   v1.28.3
k8s-node6   Ready    <none>          61s    v1.28.3

$ kubectl get all -A
NAMESPACE      NAME                                    READY   STATUS    RESTARTS   AGE
kube-flannel   pod/kube-flannel-ds-gz2hk               1/1     Running   0          97s
kube-flannel   pod/kube-flannel-ds-hg2jv               1/1     Running   0          22s
kube-flannel   pod/kube-flannel-ds-pcv8v               1/1     Running   0          46s
kube-flannel   pod/kube-flannel-ds-vb5gr               1/1     Running   1          24m
kube-system    pod/coredns-5dd5756b68-67dvx            1/1     Running   1          30m
kube-system    pod/coredns-5dd5756b68-qtd4k            1/1     Running   1          30m
kube-system    pod/etcd-k8s-node1                      1/1     Running   6          30m
kube-system    pod/kube-apiserver-k8s-node1            1/1     Running   5          30m
kube-system    pod/kube-controller-manager-k8s-node1   1/1     Running   11         30m
kube-system    pod/kube-proxy-2vhl6                    1/1     Running   0          97s
kube-system    pod/kube-proxy-ddnxk                    1/1     Running   1          30m
kube-system    pod/kube-proxy-fjmft                    1/1     Running   0          22s
kube-system    pod/kube-proxy-w2x8c                    1/1     Running   0          46s
kube-system    pod/kube-scheduler-k8s-node1            1/1     Running   11         30m

NAMESPACE     NAME                 TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)                  AGE
default       service/kubernetes   ClusterIP   10.96.0.1    <none>        443/TCP                  30m
kube-system   service/kube-dns     ClusterIP   10.96.0.10   <none>        53/UDP,53/TCP,9153/TCP   30m

NAMESPACE      NAME                             DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
kube-flannel   daemonset.apps/kube-flannel-ds   4         4         4       4            4           <none>                   24m
kube-system    daemonset.apps/kube-proxy        4         4         4       4            4           kubernetes.io/os=linux   30m

NAMESPACE     NAME                      READY   UP-TO-DATE   AVAILABLE   AGE
kube-system   deployment.apps/coredns   2/2     2            2           30m

NAMESPACE     NAME                                 DESIRED   CURRENT   READY   AGE
kube-system   replicaset.apps/coredns-5dd5756b68   2         2         2       30m