Python 纤毛荚等待使用kuberspay
环境： Openstack与Ubuntu虚拟机 Kuberspay使用Cilium作为网络插件安装kubernetes 安装后： root@admin01：/home/ubuntu#kubectl getpods-o-wide——所有名称空间Python 纤毛荚等待使用kuberspay,python,kubernetes,Python,Kubernetes,环境： Openstack与Ubuntu虚拟机 Kuberspay使用Cilium作为网络插件安装kubernetes 安装后： root@admin01：/home/ubuntu#kubectl getpods-o-wide——所有名称空间 NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED N
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
kube-system cilium-4c4jb 1/1 Running 0 5d4h 10.224.222.92 work003 <none> <none>
kube-system cilium-78tmj 1/1 Running 0 5d4h 10.224.222.90 admin02 <none> <none>
kube-system cilium-8sgck 1/1 Running 0 5d4h 10.224.222.52 admin03 <none> <none>
kube-system cilium-k2pck 1/1 Running 0 5d4h 10.224.222.107 work001 <none> <none>
kube-system cilium-kzjxk 1/1 Running 0 5d4h 10.224.222.64 admin01 <none> <none>
kube-system cilium-nfpf5 1/1 Running 0 5d4h 10.224.222.79 work002 <none> <none>
kube-system cilium-operator-5d74fc4fd6-jqpjc 0/1 Pending 0 16h <none> <none> <none> <none>
kube-system coredns-58687784f9-5j67p 0/1 Pending 0 16h <none> <none> <none> <none>
kube-system dns-autoscaler-79599df498-pxr6x 0/1 Pending 0 16h <none> <none> <none> <none>
root@admin01:/etc/cni/net.d# cat 05-cilium.conf
{
"name": "cilium",
"type": "cilium-cni"
}
root@admin01:/home/ubuntu# kubectl describe node
Name: admin01
Roles: master
Labels: beta.kubernetes.io/arch=amd64
beta.kubernetes.io/os=linux
kubernetes.io/arch=amd64
kubernetes.io/hostname=admin01
kubernetes.io/os=linux
node-role.kubernetes.io/master=
Annotations: io.cilium.network.ipv4-cilium-host: 10.233.64.1
io.cilium.network.ipv4-health-ip: 10.233.64.140
io.cilium.network.ipv4-pod-cidr: 10.233.64.0/24
kubeadm.alpha.kubernetes.io/cri-socket: /var/run/dockershim.sock
node.alpha.kubernetes.io/ttl: 0
volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp: Thu, 05 Dec 2019 22:10:05 +0000
Taints: node-role.kubernetes.io/master:NoSchedule
node.kubernetes.io/not-ready:NoSchedule
Unschedulable: false
Conditions:
Type Status LastHeartbeatTime LastTransitionTime Reason Message
---- ------ ----------------- ------------------ ------ -------
NetworkUnavailable False Thu, 05 Dec 2019 22:12:23 +0000 Thu, 05 Dec 2019 22:12:23 +0000 CiliumIsUp Cilium is running on this node
MemoryPressure False Thu, 12 Dec 2019 02:12:56 +0000 Thu, 05 Dec 2019 22:09:59 +0000 KubeletHasSufficientMemory kubelet has sufficient memory available
DiskPressure False Thu, 12 Dec 2019 02:12:56 +0000 Thu, 05 Dec 2019 22:09:59 +0000 KubeletHasNoDiskPressure kubelet has no disk pressure
PIDPressure False Thu, 12 Dec 2019 02:12:56 +0000 Thu, 05 Dec 2019 22:09:59 +0000 KubeletHasSufficientPID kubelet has sufficient PID available
Ready False Thu, 12 Dec 2019 02:12:56 +0000 Thu, 05 Dec 2019 22:09:59 +0000 KubeletNotReady runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized
Addresses:
InternalIP: 10.224.222.64
Hostname: admin01
Capacity:
cpu: 2
ephemeral-storage: 81120644Ki
hugepages-1Gi: 0
hugepages-2Mi: 0
memory: 4039464Ki
pods: 110
Allocatable:
cpu: 1800m
ephemeral-storage: 74760785387
hugepages-1Gi: 0
hugepages-2Mi: 0
memory: 3437064Ki
pods: 110
System Info:
Machine ID: 051d190f0ef34b08ac10f08827a564ed
System UUID: 051D190F-0EF3-4B08-AC10-F08827A564ED
Boot ID: 48689d4e-bba2-4f69-85fd-4ec4b12981c5
Kernel Version: 4.15.0-42-generic
OS Image: Ubuntu 18.04.1 LTS
Operating System: linux
Architecture: amd64
Container Runtime Version: docker://18.9.7
Kubelet Version: v1.16.3
Kube-Proxy Version: v1.16.3
PodCIDR: 10.233.64.0/24
PodCIDRs: 10.233.64.0/24
Non-terminated Pods: (6 in total)
Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits AGE
--------- ---- ------------ ---------- --------------- ------------- ---
kube-system cilium-kzjxk 100m (5%) 500m (27%) 64M (1%) 500M (14%) 6d4h
kube-system kube-apiserver-admin01 250m (13%) 0 (0%) 0 (0%) 0 (0%) 6d4h
kube-system kube-controller-manager-admin01 200m (11%) 0 (0%) 0 (0%) 0 (0%) 6d4h
kube-system kube-proxy-r9mk6 0 (0%) 0 (0%) 0 (0%) 0 (0%) 44h
kube-system kube-scheduler-admin01 100m (5%) 0 (0%) 0 (0%) 0 (0%) 6d4h
kube-system nodelocaldns-6wj8x 100m (5%) 0 (0%) 70Mi (2%) 170Mi (5%) 6d4h
Allocated resources:
(Total limits may be over 100 percent, i.e., overcommitted.)
Resource Requests Limits
-------- -------- ------
cpu 750m (41%) 500m (27%)
memory 137400320 (3%) 678257920 (19%)
ephemeral-storage 0 (0%) 0 (0%)
Events: <none>
root@admin01：/home/ubuntu#kubectl描述节点
姓名：admin01
角色：硕士
标签：beta.kubernetes.io/arch=amd64
beta.kubernetes.io/os=linux
kubernetes.io/arch=amd64
kubernetes.io/hostname=admin01
kubernetes.io/os=linux
node-role.kubernetes.io/master=
注释：io.cilium.network.ipv4-cilium-host:10.233.64.1
io.cilium.network.ipv4-health-ip:10.233.64.140
io.cilium.network.ipv4-pod-cidr:10.233.64.0/24
kubeadm.alpha.kubernetes.io/cri-socket:/var/run/dockershim.sock
node.alpha.kubernetes.io/ttl:0
volumes.kubernetes.io/controller-managed-attach-detach:true
CreationTimestamp:2019年12月5日星期四22:10:05+0000
污点：节点角色.kubernetes.io/master:NoSchedule
node.kubernetes.io/not ready:NoSchedule
计划外：错误
条件：
键入状态LastHeartbeatTime LastTransitionTime原因消息
---- ------ ----------------- ------------------ ------ -------
NetworkUnavailable False Thu，2019年12月5日22:12:23+0000 Thu，2019年12月5日22:12:23+0000 CiliumIsUp Cilium正在该节点上运行
MemoryPressure False Thu，2019年12月12日02:12:56+0000 Thu，2019年12月5日22:09:59+0000 Kubelethassufficient内存kubelet有足够的可用内存
DiskPressure False Thu，2019年12月12日02:12:56+0000 Thu，2019年12月5日22:09:59+0000 KubelethasNodeDiskPressure kubelet无圆盘压力
PID压力假Thu，2019年12月12日02:12:56+0000 Thu，2019年12月5日22:09:59+0000 Kubelethassufficient PID kubelet有足够的可用PID
Ready False Thu，2019年12月12日02:12:56+0000 Thu，2019年12月5日22:09:59+0000 KubeletNotReady运行时网络未就绪：NetworkReady=False原因：NetworkPluginTready消息：docker:网络插件未就绪：cni配置未初始化
地址：
内部IP:10.224.222.64
主机名：admin01
容量：
中央处理器：2
短暂存储：81120644Ki
hugepages-1Gi:0
hugepages-2Mi:0
内存：4039464Ki
豆荚：110
可分配：
cpu:1800m
短暂存储：74760785387
hugepages-1Gi:0
hugepages-2Mi:0
内存：3437064Ki
豆荚：110
系统信息：
机器ID:051d190f0ef34b08ac10f08827a564ed
系统UUID:051D190F-0EF3-4B08-AC10-F08827A564ED
启动ID:48689d4e-bba2-4f69-85fd-4ec4b12981c5
内核版本：4.15.0-42-generic
操作系统映像：Ubuntu 18.04.1 LTS
操作系统：linux
架构：amd64
容器运行时版本：docker://18.9.7
Kubelet版本：v1.16.3
Kube代理版本：v1.16.3
PodCIDR:10.233.64.0/24
苹果酒：10.233.64.0/24
非端接吊舱：（共6个）
命名空间名称CPU请求CPU限制内存请求内存限制使用年限
--------- ---- ------------ ---------- --------------- ------------- ---
kube系统纤毛kzjxk 100m（5%）500m（27%）64M（1%）500m（14%）6d4h
kube系统kube-apiserver-admin01 250m（13%）0（0%）0（0%）0（0%）6d4h
kube系统kube-controller-manager-admin01 200米（11%）0（0%）0（0%）0（0%）6小时
kube系统kube-proxy-r9mk6 0（0%）0（0%）0（0%）0（0%）44h
kube系统kube-scheduler-admin01 100m（5%）0（0%）0（0%）0（0%）6d4h
kube系统nodelocaldns-6wj8x 100m（5%）0（0%）70Mi（2%）170Mi（5%）6d4h
分配的资源：
（总限额可能超过100%，即超额承诺。）
资源请求限制
-------- -------- ------
cpu 750m（41%）500m（27%）
内存137400320（3%）678257920（19%）
短期存储量0（0%）0（0%）
活动：
Cilium是否需要比其他网络插件更多的CPU资源？我是否应该为kubernetes管理员节点分配更多的CPU资源？旧版本的cilium和最新的kubernetes群集之间存在一些错误。Kubespray已经发布了补丁，请参考此链接：你好，quyadong，欢迎访问SO。这条信息准确地描述了问题所在——也许阅读这些信息会帮助你在豆荚中增加容忍度，或者从你的节点中去除污点是的，我明白了。但是我想知道为什么cilium存在这个问题，但是其他网络插件在使用kubespray时工作得很好。而其他POD，比如coredns和dns autoscaler，遇到了同样的问题，但是它们共享相同的kubespray设置，为什么Cilium网络插件中存在问题？你能更新你的问题并包括
kubectl descripe node | grep-i污点的输出吗root@admin01:/etc/cni/net.d# cat 05-cilium.conf
{
"name": "cilium",
"type": "cilium-cni"
}
root@admin01:/home/ubuntu# kubectl describe node
Name: admin01
Roles: master
Labels: beta.kubernetes.io/arch=amd64
beta.kubernetes.io/os=linux
kubernetes.io/arch=amd64
kubernetes.io/hostname=admin01
kubernetes.io/os=linux
node-role.kubernetes.io/master=
Annotations: io.cilium.network.ipv4-cilium-host: 10.233.64.1
io.cilium.network.ipv4-health-ip: 10.233.64.140
io.cilium.network.ipv4-pod-cidr: 10.233.64.0/24
kubeadm.alpha.kubernetes.io/cri-socket: /var/run/dockershim.sock
node.alpha.kubernetes.io/ttl: 0
volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp: Thu, 05 Dec 2019 22:10:05 +0000
Taints: node-role.kubernetes.io/master:NoSchedule
node.kubernetes.io/not-ready:NoSchedule
Unschedulable: false
Conditions:
Type Status LastHeartbeatTime LastTransitionTime Reason Message
---- ------ ----------------- ------------------ ------ -------
NetworkUnavailable False Thu, 05 Dec 2019 22:12:23 +0000 Thu, 05 Dec 2019 22:12:23 +0000 CiliumIsUp Cilium is running on this node
MemoryPressure False Thu, 12 Dec 2019 02:12:56 +0000 Thu, 05 Dec 2019 22:09:59 +0000 KubeletHasSufficientMemory kubelet has sufficient memory available
DiskPressure False Thu, 12 Dec 2019 02:12:56 +0000 Thu, 05 Dec 2019 22:09:59 +0000 KubeletHasNoDiskPressure kubelet has no disk pressure
PIDPressure False Thu, 12 Dec 2019 02:12:56 +0000 Thu, 05 Dec 2019 22:09:59 +0000 KubeletHasSufficientPID kubelet has sufficient PID available
Ready False Thu, 12 Dec 2019 02:12:56 +0000 Thu, 05 Dec 2019 22:09:59 +0000 KubeletNotReady runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized
Addresses:
InternalIP: 10.224.222.64
Hostname: admin01
Capacity:
cpu: 2
ephemeral-storage: 81120644Ki
hugepages-1Gi: 0
hugepages-2Mi: 0
memory: 4039464Ki
pods: 110
Allocatable:
cpu: 1800m
ephemeral-storage: 74760785387
hugepages-1Gi: 0
hugepages-2Mi: 0
memory: 3437064Ki
pods: 110
System Info:
Machine ID: 051d190f0ef34b08ac10f08827a564ed
System UUID: 051D190F-0EF3-4B08-AC10-F08827A564ED
Boot ID: 48689d4e-bba2-4f69-85fd-4ec4b12981c5
Kernel Version: 4.15.0-42-generic
OS Image: Ubuntu 18.04.1 LTS
Operating System: linux
Architecture: amd64
Container Runtime Version: docker://18.9.7
Kubelet Version: v1.16.3
Kube-Proxy Version: v1.16.3
PodCIDR: 10.233.64.0/24
PodCIDRs: 10.233.64.0/24
Non-terminated Pods: (6 in total)
Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits AGE
--------- ---- ------------ ---------- --------------- ------------- ---
kube-system cilium-kzjxk 100m (5%) 500m (27%) 64M (1%) 500M (14%) 6d4h
kube-system kube-apiserver-admin01 250m (13%) 0 (0%) 0 (0%) 0 (0%) 6d4h
kube-system kube-controller-manager-admin01 200m (11%) 0 (0%) 0 (0%) 0 (0%) 6d4h
kube-system kube-proxy-r9mk6 0 (0%) 0 (0%) 0 (0%) 0 (0%) 44h
kube-system kube-scheduler-admin01 100m (5%) 0 (0%) 0 (0%) 0 (0%) 6d4h
kube-system nodelocaldns-6wj8x 100m (5%) 0 (0%) 70Mi (2%) 170Mi (5%) 6d4h
Allocated resources:
(Total limits may be over 100 percent, i.e., overcommitted.)
Resource Requests Limits
-------- -------- ------
cpu 750m (41%) 500m (27%)
memory 137400320 (3%) 678257920 (19%)
ephemeral-storage 0 (0%) 0 (0%)
Events: <none>