Open CharlesQQ opened 1 day ago
As we talked at today's community meeting. It is not about proposing to add a sub-command to CLI. It's essentially a requirement of cluster failover.
We have to explore the ideal solutions further after you provide more details about how you deploy workloads by PropagationPolicy.
What would you like to be added: karmadactl adds update parameter for modifying cluster resource objects
karmadactl update member-cluster1 --kubeconfig=/etc/kubernetes/kubeconfig --cluster-kubeconfig=member-kube-config/kube-001.yaml
Why is this needed: For Now, we have a large number of services deployed only in cluster A; one day, the IDC where cluster A is located failed, and all the machines were unavailable. We found a backup cluster A', hoping that A' would serve as a mirror of A. , can take over from A as soon as possible without having to modify PP in batches; Modify the cluster object of A to A', and the name remains unchanged. After the modification, you can restart the karmada controller and karmada scheduler; let new pods be created on the A' cluster as soon as possible