参照 这个链接 https://blog.51cto.com/14143894/2463392?source=drh 做的
root@node122:/etc/cni/net.d# kubectl get node —show-labels
NAME STATUS ROLES AGE VERSION LABELS
node120 Ready master 12h v1.18.1 beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/arch=amd64,kubernetes.io/hostname=node120,kubernetes.io/os=linux,node-role.kubernetes.io/master=
node121 Ready
node122 Ready
root@node122:/etc/cni/net.d# cd /
root@node122:/# cat node121.yaml
cat: node121.yaml: No such file or directory
root@node122:/# cd /root
root@node122:~# cat node121.yaml
apiVersion: projectcalico.org/v3
kind: Node
metadata:
annotations:
projectcalico.org/kube-labels: ‘{“beta.kubernetes.io/arch”:”amd64”,”beta.kubernetes.io/os”:”linux”,”kubernetes.io/arch”:”amd64”,”kubernetes.io/hostname”:”node121”,”kubernetes.io/os”:”linux”}’
creationTimestamp: “2020-12-06T15:29:03Z”
labels:
beta.kubernetes.io/arch: amd64
beta.kubernetes.io/os: linux
kubernetes.io/arch: amd64
kubernetes.io/hostname: node121
kubernetes.io/os: linux
name: node121
resourceVersion: “108399”
uid: a77e209d-a0f5-44c0-9c71-45e6a9a8d55a
spec:
addresses:
- address: 10.10.10.121/24
- address: 10.10.10.121
bgp:
ipv4Address: 10.10.10.121/24
routeReflectorClusterID: 244.0.0.1
orchRefs:
- nodeName: node121
orchestrator: k8s
status:
podCIDRs:
- 192.168.0.0/16
root@node122:~# calicoctl apply -f node121.yaml
Failed to apply ‘Node’ resource: [update conflict: Node(node121)]
现在 出错信息:
root@node122:/var/log# calicoctl —log-level=info apply -f /root/node121_new.yaml (它这个—log-level 是要在 前面)
*
INFO[0000] Log level set to info
INFO[0000] Executing config command
INFO[0000] Processing type &{map[apiVersion:projectcalico.org/v3 kind:Node metadata:map[annotations:map[projectcalico.org/kube-labels:{“beta.kubernetes.io/arch”:”amd64”,”beta.kubernetes.io/os”:”linux”,”kubernetes.io/arch”:”amd64”,”kubernetes.io/hostname”:”node121”,”kubernetes.io/os”:”linux”,”route-reflector”:”true”}] creationTimestamp:2020-12-06T15:29:03Z labels:map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux kubernetes.io/arch:amd64 kubernetes.io/hostname:node121 kubernetes.io/os:linux] name:node121 resourceVersion:113452 uid:a77e209d-a0f5-44c0-9c71-45e6a9a8d55a] spec:map[addresses:[map[address:10.10.10.121/24] map[address:10.10.10.121]] bgp:map[ipv4Address:10.10.10.121/24] orchRefs:[map[nodeName:node121 orchestrator:k8s]]] status:map[podCIDRs:[192.168.1.0/24]]]}
INFO[0000] Found resource helper: Resource(&TypeMeta{Kind:Node,APIVersion:projectcalico.org/v3,} projectcalico.org/v3, Kind=Node)
INFO[0000] Type of unpacked data: v3.Node. Unpacked &{TypeMeta:{Kind:Node APIVersion:projectcalico.org/v3} ObjectMeta:{Name:node121 GenerateName: Namespace: SelfLink: UID:a77e209d-a0f5-44c0-9c71-45e6a9a8d55a ResourceVersion:113452 Generation:0 CreationTimestamp:2020-12-06 07:29:03 -0800 PST DeletionTimestamp:
INFO[0000] Finished parsing numResources=1 source=/root/node121_new.yaml
INFO[0000] Converting resource to slice: [0xc0004b24e0]
INFO[0000] Converting resource to slice: &{{Node projectcalico.org/v3} {node121 a77e209d-a0f5-44c0-9c71-45e6a9a8d55a 113452 0 2020-12-06 07:29:03 -0800 PST
INFO[0000] Returning slice: [0xc0004b24e0]
INFO[0000] Returning slice: [0xc0004b24e0]
INFO[0000] Config file: /etc/calico/calicoctl.cfg cannot be read - reading config from environment
INFO[0000] Loaded client config: apiconfig.CalicoAPIConfigSpec{DatastoreType:”kubernetes”, EtcdConfig:apiconfig.EtcdConfig{EtcdEndpoints:””, EtcdDiscoverySrv:””, EtcdUsername:””, EtcdPassword:””, EtcdKeyFile:””, EtcdCertFile:””, EtcdCACertFile:””, EtcdKey:””, EtcdCert:””, EtcdCACert:””}, KubeConfig:apiconfig.KubeConfig{Kubeconfig:”/root/.kube/config”, K8sAPIEndpoint:””, K8sKeyFile:””, K8sCertFile:””, K8sCAFile:””, K8sAPIToken:””, K8sInsecureSkipTLSVerify:false, K8sDisableNodePoll:false, K8sUsePodCIDR:false, KubeconfigInline:””, K8sClientQPS:0}}
INFO[0000] Client: {{{CalicoAPIConfig projectcalico.org/v3} { 0 {{0 0
WARN[0000] Operation Create is not supported on Node type
INFO[0000] results: {FileInvalid:false NumResources:1 NumHandled:0 Err:
Failed to apply ‘Node’ resource: [update conflict: Node(node121)]
此问题已经解决