Integrate Existing etcd Clusters with etcd-druid
#957
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Introduced `ExistingCluster` struct in `EtcdConfig` to specify configuration for an existing etcd cluster. - Added `MemberURLs` and `Endpoint` fields to `ExistingCluster` to define the URLs and endpoint of the existing etcd cluster members.
…ruid managed cluster
- Updated `prepareInitialCluster` function to include existing cluster member URLs. - Modified `getBackupRestoreContainerCommandArgs` to append existing cluster endpoint to service endpoints.
gardener-robot
added
area/control-plane
gardener-robot-ci-2
added
the
reviewed/ok-to-test
gardener-robot-ci-1
added
needs/ok-to-test
|
/test pull-etcd-druid-unit |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
How to categorize this PR?
/area control-plane
/area high-availability
/kind enhancement
What this PR does / why we need it:
This PR introduces the necessary changes to
etcd-druidto enable seamless migration of existingetcdclusters intoetcd-druidmanaged clusters. It includes updates to the API to support theexistingClusterconfiguration, which allows clusters that are not initially managed byetcd-druidto be integrated without disruption.A step-by-step guide is added to demonstrate how to migrate an unmanaged etcd cluster to an etcd-druid managed cluster. By leveraging the
existingClusterfeature, you can create anEtcdCR configured with your current cluster’s peer URLs and endpoints, prompting etcd-druid to join your existing members. Once the newly managed members are active, you can safely remove the old, unmanaged members. This approach offers a straightforward migration path with minimal downtime.Which issue(s) this PR fixes:
Fixes #956
Special notes for your reviewer:
Release note: