-
Notifications
You must be signed in to change notification settings - Fork 461
operator: refactor bootstrapping to allow non-bootstrap manifests #226
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
operator: refactor bootstrapping to allow non-bootstrap manifests #226
Conversation
|
/retest |
|
/test images |
|
/test e2e-aws |
|
Can you elaborate slightly on what problem this is solving? |
|
/test e2e-aws |
1 similar comment
|
/test e2e-aws |
983e37f to
ea56836
Compare
openshift/machine-config-operator#226 sets up all the `manifests` required to approve CSRs for masters
updated the PR description. |
|
/retest |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinavdahiya, ashcrow The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test e2e-aws |
Bug 1788676: keep tbr inaccessible clusteroperator reason set (bootstrap removed)
This allows MCO bootstrap to render manifests in
/mainfeststhat are pushed to cluster using bootstrap node.MCO in bootstrap mode has 3 sets of assets.
bootstrap/manifests-> used by bootstrap MCC.bootstrap- > MCC+MCS bootstrap pod.manifests- > manifests installed during cluster bootstrap. eg the clusterrolebindings to allow master node boostrapping.Previously MCO in bootstrap mode only supported 1 and 3. This PR allows all three.
The MCC+MCS bootstrap pod has a
v2to support all the directory changes.See: openshift/installer#879 why this was needed in the first place.