Skip to content
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

Merged
merged 1 commit into from
Jul 15, 2021

Conversation

jan-est
Copy link
Contributor

@jan-est jan-est commented Jul 7, 2021

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.

@metal3-io-bot metal3-io-bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jul 7, 2021
@jan-est jan-est force-pushed the move-bmo-outside-camp3-jan branch from 598966d to ebca48c Compare July 7, 2021 10:28
@jan-est
Copy link
Contributor Author

jan-est commented Jul 7, 2021

/test-integration

@jan-est jan-est force-pushed the move-bmo-outside-camp3-jan branch from ebca48c to 7d62464 Compare July 8, 2021 06:09
@jan-est
Copy link
Contributor Author

jan-est commented Jul 8, 2021

/test-integration

@jan-est jan-est force-pushed the move-bmo-outside-camp3-jan branch from 7d62464 to 9844209 Compare July 8, 2021 06:29
@jan-est
Copy link
Contributor Author

jan-est commented Jul 8, 2021

/test-integration

@jan-est jan-est force-pushed the move-bmo-outside-camp3-jan branch 2 times, most recently from 75b21cb to 408bbdb Compare July 8, 2021 07:35
@metal3-io-bot metal3-io-bot added the needs-rebase Indicates that a PR cannot be merged because it has merge conflicts with HEAD. label Jul 8, 2021
@jan-est jan-est force-pushed the move-bmo-outside-camp3-jan branch from 408bbdb to ae95a64 Compare July 8, 2021 10:27
@metal3-io-bot metal3-io-bot removed the needs-rebase Indicates that a PR cannot be merged because it has merge conflicts with HEAD. label Jul 8, 2021
@jan-est jan-est force-pushed the move-bmo-outside-camp3-jan branch from ae95a64 to 30846a8 Compare July 9, 2021 06:51
@jan-est jan-est changed the title WIP: Move BMO deployment from CAPM3 Move BMO deployment from CAPM3 Jul 13, 2021
@metal3-io-bot metal3-io-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 13, 2021
Copy link
Member

@furkatgofurov7 furkatgofurov7 left a 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

@metal3-io-bot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@metal3-io-bot metal3-io-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 15, 2021
@furkatgofurov7
Copy link
Member

/retitle ⚠️ Move BMO deployment from CAPM3

@metal3-io-bot metal3-io-bot changed the title Move BMO deployment from CAPM3 ⚠️ Move BMO deployment from CAPM3 Jul 15, 2021
@fmuyassarov
Copy link
Member

/lgtm

@metal3-io-bot metal3-io-bot added the lgtm Indicates that a PR is ready to be merged. label Jul 15, 2021
@fmuyassarov fmuyassarov merged commit 41a7aba into metal3-io:master Jul 15, 2021
@kashifest kashifest deleted the move-bmo-outside-camp3-jan branch August 23, 2022 09:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants