-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[WIP] *: add logic for cluster-etcd-operator toggle #2608
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
[WIP] *: add logic for cluster-etcd-operator toggle #2608
Conversation
|
/test e2e-aws |
|
adding DNS for other cloud providers |
ffd10f8 to
58545f4
Compare
|
Just reread your PR:
|
2a4900a to
a7e55c1
Compare
|
@patrickdillon I will clean this all up before we get to merging time. |
|
Curious about general thoughts. The idea for this PR is to set CEO up for full testing. But we are testing with CEO disabled which would be the result if we had to revert. |
| records = [var.etcd_ip_addresses[count.index]] | ||
| } | ||
|
|
||
| resource "aws_route53_record" "bootstrap_a_node" { |
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.
nit, we try to keep all the bootstrap resources ie resources that are used by bootstrap-host and should be deleted when bootstrapping is complete, in the bootstrap module.
So I think a better way would be to pass the internal_zone_id, cluster_domain to the bootstrap module and create the dns record there??
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.
We would like to resolve this in a patch after this PR if possible.
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.
We would like to resolve this in a patch after this PR if possible.
hmm, this shouldn't be too much change..
just want to make sure we don't delete resources that aren't meant to be deleted..
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.
agreed
|
/retest |
|
/skip |
data/data/aws/route53/base.tf
Outdated
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.
["${var.bootstrap_ip_address}"] -> var.bootstrap_ip_address
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.
["${var.bootstrap_ip_address}"] -> [var.bootstrap_ip_address] didn't realize that the records needed a list.
data/data/azure/dns/dns.tf
Outdated
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.
https://github.com/openshift/installer/pull/2608/files#diff-1dd6be44797de18d5c235fc324f8ee2aR92
i think this should be something like https://github.com/openshift/installer/pull/2608/files#diff-764adb23dcc0edbbebc09192eb233e9aR3
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.
not sure why you needs these volumes?
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.
why do we start the etcd member here?
https://github.com/openshift/installer/pull/2608/files#diff-ce82c1d8a44f7dfc41dfc024085ccfeeR200
but the bootstrap-apiserver puts the manifests to be run when bootstrapping the cluster..
Is it because we think the lifecycle of that pod is separate from the bootstrap-control-plane
f46adcc to
d364191
Compare
|
/retest |
d364191 to
3158e81
Compare
Signed-off-by: Sam Batschelet <[email protected]>
Signed-off-by: Sam Batschelet <[email protected]>
Signed-off-by: Sam Batschelet <[email protected]>
Signed-off-by: Sam Batschelet <[email protected]>
Signed-off-by: Sam Batschelet <[email protected]>
3158e81 to
b7e62e4
Compare
|
FTR will rebase this into something reasonable when I am done with the review. |
|
@hexfusion: The following tests 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. |
|
We have reworked this into a simpler solution, continued here #2730 |
NOTE cluster-etcd-operator is out for 4.3
In 4.3 cluster-etcd-operator will take over the process of bootstrapping the etcd cluster. To provide a clear path to disable/revert these changes we have setup the following conditional logic.
MCO: The MCO render command invoked in bootkube has a new optional flag to pass the value of the
cluster-etcd-operatorimage[1]. The availability of this flags value[2] is used to conditionally adjust theetcd-memberstatic pod spec allowing it to use the new bootstrapping method via the operator or fall back to the 4.2 SRV method.Installer: The installer in 4.3 has a few notable changed introduced by this PR. First of all the
rendercommand populates a static pod manifest which creates a single member etcd cluster. After we have the single node cluster we can progress and cluster-operator can be deployed. This speeds up the time it takes for the operators to begin to reconcile as we are no longer waiting for all 3 etcds to bootstrap before we progress the operators.cluster-etcd-operator: CEO is currently set as Unmanaged[3]. This allows us to include the CEO in CVO operator payload while setting the controllers to perform noop. This short term phase allows us to merge this PR proving that we can at the same time have CEO included in CVO but still use the old SRV bootstrap.
Revert Plan: If a case existed where we had a design error and the operator needed to be pulled from 4.3.
:
[1] https://github.com/openshift/installer/pull/2608/files#diff-ce82c1d8a44f7dfc41dfc024085ccfeeR298
[2] https://github.com/openshift/machine-config-operator/blob/bd846958bc95d049547164046a962054fca093df/templates/master/00-master/_base/files/etc-kubernetes-manifests-etcd-member.yaml#L22
[3] https://github.com/openshift/cluster-etcd-operator/blob/master/manifests/0000_12_etcd-operator_01_operator.cr.yaml#L8
Depends on: