-
Notifications
You must be signed in to change notification settings - Fork 87
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
⚠️ Move BMO deployment from CAPM3 #242
⚠️ Move BMO deployment from CAPM3 #242
Conversation
598966d
to
ebca48c
Compare
/test-integration |
ebca48c
to
7d62464
Compare
/test-integration |
7d62464
to
9844209
Compare
/test-integration |
75b21cb
to
408bbdb
Compare
408bbdb
to
ae95a64
Compare
ae95a64
to
30846a8
Compare
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 needs m3-dev-env PR to pass the CI and other way around. We need to force merge it.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: furkatgofurov7, lentzi90 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 |
/retitle |
/lgtm |
To be able to support new Cluster API multitenancy model in CAPM3 v1alpha5, we need to take BMO deployment out. Meaning that users using CAPM3 v1alpha5 should deploy BMO separately to their clusters.