-
Notifications
You must be signed in to change notification settings - Fork 69
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
[KONFLUX-179]: ADR for provisioning clusters #172
Conversation
This ADR replaces #168. |
@dperaza4dustbit, @gbenhaim I'd love to see your review comments to this proposal. |
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.
Thanks for writing this up, @amisstea!
This dictates how clusters will be provisioned from within an integration pipeline using the Cluster as a Service Operator. Signed-off-by: Alex Misstear <[email protected]>
Signed-off-by: Alex Misstear <[email protected]>
c847866
to
a6f563b
Compare
Signed-off-by: Alex Misstear <[email protected]>
a6f563b
to
9a571c7
Compare
Superfluous OIDC config details are also removed. Signed-off-by: Alex Misstear <[email protected]>
@arewm could you please give this another review pass? |
Remove some uneccesary parenthesis as well. Signed-off-by: Alex Misstear <[email protected]>
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.
This looks good, there will be no need for changes to KubeSaw as tiers are being decoupled from Host Operator and can be managed independent in Infra deployment or what ever mechanism we use upstream for Konflux install/upate
This dictates how clusters will be provisioned from within an integration pipeline using the Cluster as a Service Operator.