cluster-api: Using external etcd can not update kcp status
What steps did you take and what happened:
- I use external etcd for kcp and refer to the document https://github.com/kubernetes-sigs/cluster-api/blob/6dc38f9b64691822ccbefc8c08ae4a49b474f602/bootstrap/kubeadm/docs/external-etcd.md.
- There is an error that the etcd tls.key could not be obtained when the KCP controller updated the status.
- Then I add tls.key for CLUSTER-NAME-etcd but I get the error is that etcd unhealthy.
- I see kcp controller call the function updateStatus and updateStatus will call GetWorkloadCluster, GetWorkloadCluster will use etcd tls.key and tls.crt to get etcd client, then the client will be used for get the etcd pods in cluster.
- So can I think that cluster-api does not support external-etcd yet.
What did you expect to happen: I expect the kcp status can update but I can not find the method for external etcd or my understanding is wrong.
Anything else you would like to add:
Environment:
- Cluster-api version: v0.3.5
- Minikube/KIND version:
- Kubernetes version: (use
kubectl version): v1.17.4 - OS (e.g. from
/etc/os-release):
/kind bug [One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels]
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 16 (13 by maintainers)
@zanghao2 PTAL to the related PR, it will be great to have you opinion on the proposed changes
@vincepri It’s called out specifically in the goals section: “To support pre-existing, user-managed, external etcd clusters”, and the scenario is also called out in the behavioral sections as it applies to the various operations