K8s 安装:修订间差异
跳到导航
跳到搜索
第141行: | 第141行: | ||
===== kube-flannel ===== | ===== kube-flannel ===== | ||
wget https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml | wget https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml | ||
修改 net-conf.json:Network 与 pod-network-cidr 保持一致。 | |||
"Network": "10.2.0.0/16", | |||
kubectl apply -f kube-flannel.yml | kubectl apply -f kube-flannel.yml | ||
2024年3月26日 (二) 13:09的版本
环境准备
- 关闭 selinux 及 firewalld
- 关闭 Swap
host
192.168.0.158 np0 192.168.0.229 np1 192.168.0.249 np2 192.168.0.148 np3
设置网桥参数
cat << EOF > /etc/sysctl.d/99-kubernetes-cri.conf net.bridge.bridge-nf-call-ip6tables = 1 net.bridge.bridge-nf-call-iptables = 1 net.ipv4.ip_forward = 1 user.max_user_namespaces=28633 EOF sysctl -p /etc/sysctl.d/99-kubernetes-cri.conf
配置支持 IPVS
加载 ip_vs 内核模块。kube-proxy 通过采用 iptables + ipset + ipvs 的方式实现为符合条件的 Pod 提供负载均衡。否则 kube-proxy 会退回到 iptables 模式。
cat > /etc/modules-load.d/ip_vs.conf << EOF ip_vs ip_vs_rr ip_vs_wrr ip_vs_sh nf_conntrack_ipv4 EOF
modprobe ip_vs modprobe ip_vs_rr modprobe ip_vs_wrr modprobe ip_vs_sh modprobe nf_conntrack_ipv4
导入模块
cat << EOF > /etc/modules-load.d/containerd.conf overlay br_netfilter EOF
modprobe overlay modprobe br_netfilter
lsmod | grep overlay lsmod | grep br_netfilter
部署 Containerd
创建容器工具
wget https://github.com/opencontainers/runc/releases/download/v1.1.4/runc.amd64 install -m 755 runc.amd64 /usr/local/sbin/runc
容器间网络通信
wget https://github.com/containernetworking/plugins/releases/download/v1.2.0/cni-plugins-linux-amd64-v1.2.0.tgz mkdir -p /opt/cni/bin tar Cxzvf /opt/cni/bin cni-plugins-linux-amd64-v1.2.0.tgz
Containerd
wget https://github.com/containerd/containerd/releases/download/v1.7.14/containerd-1.7.14-linux-amd64.tar.gz tar Cxzvf /usr/local containerd-1.7.14-linux-amd64.tar.gz wget https://raw.githubusercontent.com/containerd/containerd/main/containerd.service -o /usr/lib/systemd/system/containerd.service systemctl daemon-reload && systemctl enable containerd
mkdir /etc/containerd containerd config default > /etc/containerd/config.toml cd /etc/containerd/ cp config.toml config.toml.orig vi config.toml [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc.options] SystemdCgroup = true # false 修改为 true [plugins."io.containerd.grpc.v1.cri"] # sandbox_image = "registry.k8s.io/pause:3.9" sandbox_image = "registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.9" [plugins."io.containerd.grpc.v1.cri".registry.mirrors] [plugins."io.containerd.grpc.v1.cri".registry.mirrors."docker.io"] endpoint = ["http://mirrors.ustc.edu.cn"] [plugins."io.containerd.grpc.v1.cri".registry.mirrors."*"] endpoint = ["http://hub-mirror.c.163.com"]
systemctl restart containerd netstat -nlput | grep containerd
kubernetes
repo
cat > /etc/yum.repos.d/kubernetes.repo << EOF [kubernetes] name=Kubernetes baseurl=https://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64/ enabled=1 gpgcheck=1 repo_gpgcheck=1 gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg https://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpg EOF
kubelet kubeadm kubectl
# yum list kubelet --showduplicates yum install kubelet kubeadm kubectl systemctl enable kubelet systemctl status kubelet 此时状态不正常,等到 init 或 join 后,状态正常。
master
INIT
安装 calico 网络插件需要 pod-network-cidr
kubeadm init \ --image-repository registry.aliyuncs.com/google_containers \ --kubernetes-version=1.28.2 \ --apiserver-advertise-address=192.168.0.249 \ --service-cidr=10.1.0.0/16 \ --pod-network-cidr=10.2.0.0/16
- apiserver-advertise-address: master 主机 IP 地址
- service-cidr: 内部 service 使用 IP 范围,不可与 pod 及 master 重复
- pod-network-cidr: k8s pod 节点之间网络通信使用 IP 范围
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/ Then you can join any number of worker nodes by running the following on each as root: kubeadm join 192.168.0.249:6443 --token z1q425.gy4kgpp491c8nkq2 --discovery-token-ca-cert-hash sha256:0b02fa4069856afb9d17dba76527b7e7c630d799cc3c00c3cc36c8beaec0128c
calico
wget https://raw.githubusercontent.com/projectcalico/calico/v3.25.0/manifests/calico.yaml kubectl apply -f calico.yaml
kube-flannel
wget https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml 修改 net-conf.json:Network 与 pod-network-cidr 保持一致。 "Network": "10.2.0.0/16",
kubectl apply -f kube-flannel.yml
Node
kubeadm join 192.168.0.249:6443 --token z1q425.gy4kgpp491c8nkq2 --discovery-token-ca-cert-hash sha256:0b02fa4069856afb9d17dba76527b7e7c630d799cc3c00c3cc36c8beaec0128c
kubelet Guide
Create token
# Expires 24h kubeadm token create --print-join-command
delete Node
- master
NODE=node3 kubectl drain ${NODE} --delete-local-data --force --ignore-daemonsets kubectl delete node ${NODE}
Node label
kubectl label node ${NODE} node-role.kubernetes.io/worker=worker kubectl label node ${NODE} node-role.kubernetes.io/master=master kubectl label node ${NODE} node-role.kubernetes.io/worker-
get Node
# ENV(master): scp /etc/kubernetes/admin.conf ${NODE}:/root/.kube/config kubectl get cs kubectl get node kubectl describe node ${NODE} kubectl get pods --all-namespaces
Error
node NotReady
kubectl apply -f calico.yaml kubectl apply -f kube-flannel.yml
dorisfe1 NotReady <none> 8s v1.28.2
registry.mirrors
即将删除的配置项
WARN[0000] DEPRECATION: The `mirrors` property of `[plugins."io.containerd.grpc.v1.cri".registry]` is deprecated since containerd v1.5 and will be removed in containerd v2.0. Use `config_path` instead.
kubectl get node
节点需要 /etc/kubernetes/admin.conf
E0325 16:13:46.489435 14081 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [::1]:8080: connect: connection refused
crictl info
# /etc/crictl.yaml runtime-endpoint: unix:///run/containerd/containerd.sock image-endpoint: unix:///run/containerd/containerd.sock timeout: 2 debug: false pull-image-on-create: false disable-pull-on-run: false
E0326 10:15:02.860305 3920 remote_runtime.go:616] "Status from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/dockershim.sock: connect: no such file or directory\""