首页 > 编程知识 正文

安装kubelet时显示没有可用的软件包,安装kubectl

时间:2023-05-06 07:56:58 阅读:244074 作者:80

1、签发kubelet证书并拷贝

vim kubelet-csr.json{ "CN": "k8s-kubelet", "hosts": [ "127.0.0.1", "10.4.7.9", "10.4.7.12", "10.4.7.13", "10.4.7.15", "10.4.7.16", "10.4.7.17", "10.4.7.18", "10.4.7.19", "10.4.7.20" ], "key": { "algo": "rsa", "size": 2048 }, "names": [ { "C": "CN", "ST": "beijing", "L": "beijing", "O": "k8s", "OU": "system" } ]}cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=server kubelet-csr.json | cfssl-json -bare kubeletscp kubelet.pem yanc7-12:/opt/kubernetes/server/bin/certsscp kubelet-key.pem yanc7-12:/opt/kubernetes/server/bin/certsscp kubelet.pem yanc7-13:/opt/kubernetes/server/bin/certsscp kubelet-key.pem yanc7-13:/opt/kubernetes/server/bin/certs

2、创建集群配置和资源

kubectl config set-cluster myk8s --certificate-authority=/opt/kubernetes/server/bin/certs/ca.pem --embed-certs=true --server=https://10.4.7.9:7443 --kubeconfig=kubelet.kubeconfigkubectl config set-credentials k8s-node --client-certificate=/opt/kubernetes/server/bin/certs/client.pem --client-key=/opt/kubernetes/server/bin/certs/client-key.pem --embed-certs=true --kubeconfig=kubelet.kubeconfigkubectl config set-context myk8s-context --cluster=myk8s --user=k8s-node --kubeconfig=kubelet.kubeconfigkubectl config use-context myk8s-context --kubeconfig=kubelet.kubeconfigvim k8s-node.yamlapiVersion: rbac.authorization.k8s.io/v1kind: ClusterRoleBindingmetadata: name: k8s-noderoleRef: apiGroup: rbac.authorization.k8s.io kind: ClusterRole name: system:nodesubjects:- apiGroup: rbac.authorization.k8s.io kind: User name: k8s-nodekubectl create -f k8s-node.yamlkubectl get clusterrolebinding k8s-nodekubectl get clusterrolebinding k8s-node -o yamlscp kubelet.kubeconfig yanc7-13:/opt/kubernetes/server/bin/conf/

3、拉取基础pause镜像并上传到harbor仓库

docker pull kubernetes/pausedocker tag f9d5de079539 harbor.yanc.com/public/pause:latestdocker push harbor.yanc.com/public/pause:latest

4、创建kubelet启动脚本和supervisor配置文件

vim /opt/kubernetes/server/bin/kubelet.sh#!/bin/sh./kubelet --anonymous-auth=false --cgroup-driver systemd --cluster-dns 192.168.0.2 --cluster-domain cluster.local --runtime-cgroups=/systemd/system.slice --kubelet-cgroups=/systemd/system.slice --fail-swap-on="false" --client-ca-file ./certs/ca.pem --tls-cert-file ./certs/kubelet.pem --tls-private-key-file ./certs/kubelet-key.pem --hostname-override yanc7-12.host.com --image-gc-high-threshold 20 --image-gc-low-threshold 10 --kubeconfig ./conf/kubelet.kubeconfig --log-dir /data/logs/kubernetes/kube-kubelet --pod-infra-container-image harbor.yanc.com/public/pause:latest --root-dir /data/kubeletchmod +x /opt/kubernetes/server/bin/kubelet.shmkdir -p /data/logs/kubernetes/kube-kubelet /data/kubeletvim /etc/supervisord.d/kube-kubelet.ini[program:kube-kubelet-7-12]command=/opt/kubernetes/server/bin/kubelet.sh ; the program (relative uses PATH, can take args)numprocs=1 ; number of processes copies to start (def 1)directory=/opt/kubernetes/server/bin ; directory to cwd to before exec (def no cwd)autostart=true ; start at supervisord start (default: true)autorestart=true ; retstart at unexpected quit (default: true)startsecs=30 ; number of secs prog must stay running (def. 1)startretries=3 ; max # of serial start failures (default 3)exitcodes=0,2 ; 'expected' exit codes for process (default 0,2)stopsignal=QUIT ; signal used to kill process (default TERM)stopwaitsecs=10 ; max num secs to wait b4 SIGKILL (default 10)user=root ; setuid to this UNIX account to run the programredirect_stderr=true ; redirect proc stderr to stdout (default false)stdout_logfile=/data/logs/kubernetes/kube-kubelet/kubelet.stdout.log ; stderr log path, NONE for none; default AUTOstdout_logfile_maxbytes=64MB ; max # logfile bytes b4 rotation (default 50MB)stdout_logfile_backups=4 ; # of stdout logfile backups (default 10)stdout_capture_maxbytes=1MB ; number of bytes in 'capturemode' (default 0)stdout_events_enabled=false ; emit events on stdout writes (default false)supervisorctl updatesupervisorctl status

此时kubelet启动有报错:
failed to run Kubelet: misconfiguration: kubelet cgroup driver: “systemd” is different from docker cgroup driver: “cgroupfs”

docker默认使用的是cgroupfs,kubelet默认使用的是systemd。两者不一致导致启动报错,相关资料可以查阅https://www.cnblogs.com/hongdada/p/9771857.html
修改vim /etc/docker/daemon.json,加入
{
“exec-opts”: [“native.cgroupdriver=systemd”]
}
systemctl daemon-reload
systemctl restart docker

然后再启动kubelet就没问题了
supervisorctl start kube-kubelet-7-12


kubectl get nodes

添加角色标签
kubectl label node yanc7-12.host.com node-role.kubernetes.io/master=
kubectl label node yanc7-12.host.com node-role.kubernetes.io/node=
kubectl label node yanc7-13.host.com node-role.kubernetes.io/master=
kubectl label node yanc7-13.host.com node-role.kubernetes.io/node=

版权声明:该文观点仅代表作者本人。处理文章:请发送邮件至 三1五14八八95#扣扣.com 举报,一经查实,本站将立刻删除。