-
Notifications
You must be signed in to change notification settings - Fork 462
setup-etcd-environment: support scaling from cluster-etcd-operator #1221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
setup-etcd-environment: support scaling from cluster-etcd-operator #1221
Conversation
|
depends on #1224, needs rebase after that gets in, thanks |
e08c0f3 to
9865cad
Compare
Is this a new test I don't think we changed this. Update: We have a fix |
|
|
/test e2e-aws |
1 similar comment
|
/test e2e-aws |
|
trying to understand this failure. /test e2e-aws |
92f4abc to
e5e4ecd
Compare
ec61312 to
8f2653b
Compare
6f6556a to
6bef5de
Compare
|
test failures related to regression in aws tests openshift/origin#24083 |
6bef5de to
38c5eaf
Compare
Signed-off-by: Sam Batschelet <[email protected]>
38c5eaf to
032ddd5
Compare
032ddd5 to
37e6851
Compare
|
/lgtm |
|
/retest |
kikisdeliveryservice
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hexfusion, kikisdeliveryservice, retroflexer The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/skip |
|
/test e2e-aws |
|
/retest |
1 similar comment
|
/retest |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
|
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@hexfusion: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
/retest |
The discovery init container is a very important part of the bootstraping process. Currently, we use SRV queries to populate ENV variables consumed by other containers in the pod.
As we move to an operator managed etcd cluster additional data points and validations need to be performed. The scaling of etcd is managed by the clustermembercontroller (CMC). When a new candidate for membership is verified as
Readyto join the cluster the CMC populates a ConfigMap with basic information for the scaling process. This information includes details on the current members of the cluster. From this information, we can then populate the ETCD_INITIAL_CLUSTER variable which directs etcd on who its peers are.To manage new candidates from racing only 1 member can scale at a time. Until that member has been added and verified no other member can be added. We do this by doing a wait until we observe the data identifying the pod as scaling.
We also populate a new ENV variable ETCD_ENDPOINTS this is used later on in the process by a new init container called membership.
Pending changes: The following items will change in the near future.
member-configConfigMap will stop using annotations for scaling data instead a more traditionaldata:key.depends on #1224