Kubernetes 如何让印花布使用K8s etcd？

我读了calico文档，上面说calico会在启动时启动一个etcd实例，但我注意到K8s集群会在集群启动时启动一个etcd pod。我希望calico使用该etcd节点，因此我执行以下操作：

使用calicoctl do test，创建一个配置文件：

# cat myconfig.yml
apiVersion: projectcalico.org/v3
kind: CalicoAPIConfig
metadata:
spec:
  datastoreType: etcdv3
  etcdEndpoints: https://10.100.1.20:2379
  etcdKeyFile: /etc/kubernetes/pki/etcd/server.key
  etcdCertFile: /etc/kubernetes/pki/etcd/server.crt
  etcdCACertFile: /etc/kubernetes/pki/etcd/ca.crt

etcd配置信息来自/etc/kubernetes/manifests/etcd.yaml

# cat /etc/kubernetes/manifests/etcd.yaml
apiVersion: v1
kind: Pod
metadata:
  annotations:
    scheduler.alpha.kubernetes.io/critical-pod: ""
  creationTimestamp: null
  labels:
    component: etcd
    tier: control-plane
  name: etcd
  namespace: kube-system
spec:
  containers:
  - command:
    - etcd
    - --advertise-client-urls=https://127.0.0.1:2379
    - --cert-file=/etc/kubernetes/pki/etcd/server.crt
    - --client-cert-auth=true
    - --data-dir=/var/lib/etcd
    - --initial-advertise-peer-urls=https://127.0.0.1:2380
    - --initial-cluster=t-k8s-a1=https://127.0.0.1:2380
    - --key-file=/etc/kubernetes/pki/etcd/server.key
    - --listen-client-urls=https://127.0.0.1:2379
    - --listen-peer-urls=https://127.0.0.1:2380
    - --name=t-k8s-a1
    - --peer-cert-file=/etc/kubernetes/pki/etcd/peer.crt
    - --peer-client-cert-auth=true
    - --peer-key-file=/etc/kubernetes/pki/etcd/peer.key
    - --peer-trusted-ca-file=/etc/kubernetes/pki/etcd/ca.crt
    - --snapshot-count=10000
    - --trusted-ca-file=/etc/kubernetes/pki/etcd/ca.crt
    image: k8s.gcr.io/etcd-amd64:3.2.18
    imagePullPolicy: IfNotPresent
    livenessProbe:
      exec:
        command:
        - /bin/sh
        - -ec
        - ETCDCTL_API=3 etcdctl --endpoints=https://[127.0.0.1]:2379 --cacert=/etc/kubernetes/pki/etcd/ca.crt
          --cert=/etc/kubernetes/pki/etcd/healthcheck-client.crt --key=/etc/kubernetes/pki/etcd/healthcheck-client.key
          get foo
      failureThreshold: 8
      initialDelaySeconds: 15
      timeoutSeconds: 15
    name: etcd
    resources: {}
    volumeMounts:
    - mountPath: /var/lib/etcd
      name: etcd-data
    - mountPath: /etc/kubernetes/pki/etcd
      name: etcd-certs
  hostNetwork: true
  priorityClassName: system-cluster-critical
  volumes:
  - hostPath:
      path: /var/lib/etcd
      type: DirectoryOrCreate
    name: etcd-data
  - hostPath:
      path: /etc/kubernetes/pki/etcd
      type: DirectoryOrCreate
    name: etcd-certs
status: {}

仍然拒绝

# calicoctl get nodes --config ./myconfig.yml
Failed to create Calico API client: dial tcp 10.100.1.20:2379: connect: connection refused


# kubectl get pods --all-namespaces -o wide
NAMESPACE     NAME                                READY     STATUS    RESTARTS   AGE       IP             NODE       NOMINATED NODE
kube-system   calico-node-5nbwz                   2/2       Running   0          22h       10.100.1.21    t-k8s-b2   <none>
kube-system   calico-node-m967m                   2/2       Running   0          22h       10.100.1.20    t-k8s-a1   <none>
kube-system   calico-typha-64fc9d86dd-g8m54       1/1       Running   0          22h       10.100.1.21    t-k8s-b2   <none>
kube-system   coredns-78fcdf6894-5thqv            1/1       Running   0          1d        192.168.1.2    t-k8s-b2   <none>
kube-system   coredns-78fcdf6894-gm5zs            1/1       Running   0          1d        192.168.1.3    t-k8s-b2   <none>
kube-system   etcd-t-k8s-a1                       1/1       Running   0          1d        10.100.1.20    t-k8s-a1   <none>
kube-system   kube-apiserver-t-k8s-a1             1/1       Running   0          1d        10.100.1.20    t-k8s-a1   <none>
kube-system   kube-controller-manager-t-k8s-a1    1/1       Running   0          1d        10.100.1.20    t-k8s-a1   <none>
kube-system   kube-proxy-9rgmd                    1/1       Running   0          1d        10.100.1.20    t-k8s-a1   <none>
kube-system   kube-proxy-z75kc                    1/1       Running   0          1d        10.100.1.21    t-k8s-b2   <none>
kube-system   kube-scheduler-t-k8s-a1             1/1       Running   0          1d        10.100.1.20    t-k8s-a1   <none>
testalex      etcd-deployment-5b5d67bb84-nr7vc    1/1       Running   0          1d        192.168.1.26   t-k8s-b2   <none>
testalex      k8s-alert-76f97ccf49-gffgb          1/1       Running   0          1d        192.168.1.18   t-k8s-b2   <none>
testalex      k8s-monitor-7ddcb74b87-75vxb        1/1       Running   0          1d        192.168.1.27   t-k8s-b2   <none>
testalex      mysql-deployment-858464457f-nznq5   1/1       Running   0          1d        192.168.1.16   t-k8s-b2   <none>

#calicoctl get节点--config./myconfig.yml
无法创建Calico API客户端：拨号tcp 10.100.1.20:2379:连接：连接被拒绝
#kubectl获得吊舱——所有名称空间——o宽
名称空间名称就绪状态重新启动IP节点指定节点
kube系统印花布节点-5nbwz 2/2运行0 22h 10.100.1.21 t-k8s-b2
kube系统印花布节点-m967m 2/2运行0 22h 10.100.1.20 t-k8s-a1
kube系统印花布-typha-64fc9d86dd-g8m54 1/1运行0 22h 10.100.1.21 t-k8s-b2
kube系统coredns-78fcdf6894-5thqv 1/1运行0 1d 192.168.1.2 t-k8s-b2
kube系统coredns-78fcdf6894-gm5zs 1/1运行0 1d 192.168.1.3 t-k8s-b2
kube系统etcd-t-k8s-a1 1/1运行0 1d 10.100.1.20 t-k8s-a1
kube系统kube-apiserver-t-k8s-a1 1/1运行0 1d 10.100.1.20 t-k8s-a1
kube系统kube-controller-manager-t-k8s-a1 1/1运行0 1d 10.100.1.20 t-k8s-a1
kube系统kube-proxy-9rgmd 1/1运行0 1d 10.100.1.20 t-k8s-a1
kube系统kube-proxy-z75kc 1/1运行0 1d 10.100.1.21 t-k8s-b2
kube系统kube-scheduler-t-k8s-a1 1/1运行0 1d 10.100.1.20 t-k8s-a1
testalex etcd-deployment-5b5d67bb84-nr7vc 1/1运行0 1d 192.168.1.26 t-k8s-b2
testalex k8s-alert-76f97ccf49-gffgb 1/1运行0 1d 192.168.1.18 t-k8s-b2
testalex k8s-monitor-7ddcb74b87-75vxb 1/1运行0 1d 192.168.1.27 t-k8s-b2
testalex mysql-deployment-858464457f-nznq5 1/1运行0 1d 192.168.1.16 t-k8s-b2

默认情况下，它将使用Kubernetes数据存储（使用etcdv3）。您在

/etc/calico/calicotl.cfg

下的

calicotl

配置应该如下所示：

apiVersion: projectcalico.org/v3
kind: CalicoAPIConfig
metadata:
spec:
  datastoreType: "kubernetes"
  kubeconfig: "/path/to/.kube/config"

这对我很有用：

calicoctl get nodes
NAME
ip-172-x-x-x.us-west-2.compute.internal
ip-172-x-x-x.us-west-2.compute.internal
ip-172-x-x-x.us-west-2.compute.internal
ip-172-x-x-x.us-west-2.compute.internal
ip-172-x-x-x.us-west-2.compute.internal
ip-172-x-x-x.us-west-2.compute.internal

---

doc说：Calico和Kubernetes API数据存储的联网是测试版，因为它还不支持Calico IPAMDo您需要IPAM吗？我看不到任何关于最新文档不受支持的内容：这是一个文档这是什么IP

10.100.1.20

？集装箱？服务器？你从哪里弄来的？这是哪个etcd集装箱的ip舱