-
Notifications
You must be signed in to change notification settings - Fork 104
Open
Labels
area/control-plane-migrationControl plane migration relatedControl plane migration relatedarea/ops-productivityOperator productivity related (how to improve operations)Operator productivity related (how to improve operations)area/performancePerformance (across all domains, such as control plane, networking, storage, etc.) relatedPerformance (across all domains, such as control plane, networking, storage, etc.) relatedarea/robustnessRobustness, reliability, resilience relatedRobustness, reliability, resilience relatedarea/scalabilityScalability relatedScalability relatedkind/enhancementEnhancement, improvement, extensionEnhancement, improvement, extension
Description
How to categorize this issue?
/area control-plane-migration high-availability ops-productivity performance robustness scalability usability
/kind enhancement
What would you like to be added:
Currently, the etcd member name is the same as the pod name of the member.
Because of this, in scenarios like Live CPM, where we want to have multiple etcd members with the same pod name, the new member cannot join the cluster.
Therefore, we want the etcd member name to be generated independently of the pod name.
Why is this needed:
The supports use cases like Live CPM
Metadata
Metadata
Assignees
Labels
area/control-plane-migrationControl plane migration relatedControl plane migration relatedarea/ops-productivityOperator productivity related (how to improve operations)Operator productivity related (how to improve operations)area/performancePerformance (across all domains, such as control plane, networking, storage, etc.) relatedPerformance (across all domains, such as control plane, networking, storage, etc.) relatedarea/robustnessRobustness, reliability, resilience relatedRobustness, reliability, resilience relatedarea/scalabilityScalability relatedScalability relatedkind/enhancementEnhancement, improvement, extensionEnhancement, improvement, extension