root@campaigns:/var/lib/dpkg/info# apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space wi
Kubernetes如何为ETCD集群创建租约资源,以查看leader信息?
$ kubectl get leases
NAME HOLDER AGE
kube-controller-manager master01.k8s-host.com_68f9a489-4e8c-4dc6-a9c2-6136d4cf7798 22h
kube-scheduler master01.k8s-host.com_b1a8a9a3-e
我正在尝试连接两个Docker主机与一个覆盖网络,并使用etcd作为一个KV商店。etcd直接在第一个主机上运行(而不是在容器中)。最后,我设法将第一个主机的Docker守护进程连接到etcd,但无法在第二个主机上建立一个连接-- Docker守护进程。
我从页面下载了etcd,并按照"Linux“部分的说明进行操作。启动etcd后,它将侦听以下端口:
etcdmain: listening for peers on http://localhost:2380
etcdmain: listening for peers on http://localhost:7001
etcdmain
我一直在努力让我的本地集群与库伯内特斯站在一起。我已经创建了二进制文件,并且正在运行名为./hack/local-up-cluster.sh的脚本。当我运行这个脚本时,我得到了这个错误:
root@ubuntu1604:~/kubernetes# ./hack/local-up-cluster.sh
+++ [0215 00:22:00] Building go targets for linux/ppc64le:
cmd/kube-apiserver
cmd/kube-controller-manager
cmd/kube-proxy
cmd/kubectl
突然,当我将一个新服务部署到这个集群中时,kubernetes集群显示了这个错误:
Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "02ceaa702704151a69b1f9f5210d4a68956c2b41050b711319f07d38f57364af": error getting ClusterInformation: Get "https://10.96.0.1:443/apis/crd.projectca
我正在构建一个registry.service.上有3个节点的Deis集群,这是建议使用Vagrant的,但是当我执行时:make run会在CoreOS上发生一些错误经过一段时间的检查,我发现所有依赖于etcd的映像都有相同的问题,所有映像都会失败或仍在等待bin/boot脚本的执行。产出:
waiting for etcd at :4001...
waiting for etcd at :4001...
waiting for etcd at :4001...
waiting for etcd at :4001...
waiting for etcd at :4001...
waiting
我试图使用AWS中的3个实例运行etcd,但是当我试图列出成员时,我会得到下面的错误:
[ec2-user@etcd1 ~]$ etcdctl member list
{"level":"warn","ts":"2021-10-19T04:50:01.981Z","logger":"etcd-client","caller":"v3/retry_interceptor.go:62","msg":"retrying of unary invoke
rke --debug up --config cluster.yml
在有错误的etcd主机上进行健康检查失败:
DEBU0281未能检查etcd主机x.x:未能获得主机x.x的/health : get ":remote error: tls:坏证书“的运行状况
检查健康检查
for endpoint in $(docker exec etcd /bin/sh -c "etcdctl member list | cut -d, -f5"); do
echo "Validating connection to ${endpoint}/health
我有一个单节点kubernetes集群在运行。一切正常,但是当我运行"kubectl get cs“(kubectl get componentstatus)时,它显示了etcd的两个实例。我只运行了一个etcd实例。
[root@master01 vagrant]# kubectl get cs NAME STATUS MESSAGE ERROR controller-manager Healthy ok scheduler Healthy ok etcd-0
我在努力学习凯尔西·海塔的“艰难之路”教程。我已经退出了脚本,因为我试图在本地服务器上引导k8s。
但是,当我创建服务时,我得到了一个错误:
Failed to start etcd.service: Unit is not loaded properly: Bad message.
See system logs and 'systemctl status etcd.service' for details.
查看日志,我得到:
Jun 21 20:16:49 controller-0 systemd[1]: [/etc/systemd/system/etcd.service
我尝试将蚀刻作为一个运行在带有波德曼的容器中的systemd服务来启动。
启动后,我从systemd获得这个错误日志:
systemd[1]: etcd.service: Got notification message from PID 4696, but reception only permitted for main PID 4868
但是etcd似乎能够开始尝试通知容器守护进程:
21T15:31:08.817Z","caller":"etcdserver/server.go:2500","msg":"cluster v
我登录了Kubernetes etcd pod
kubectl exec -it -n kube-system etcd-master -- /bin/sh
我不知道这是什么操作系统。
ls不起作用
sh-5.0# ls
sh: ls: command not found
猫不管用
sh-5.0# cat /etc/os-release
sh: cat: command not found
apt,yum未被识别
sh-5.0# apt
sh: apt: command not found
sh-5.0# yum
sh: yum: command not found
我只能通过模式扩展来cd