-
Notifications
You must be signed in to change notification settings - Fork 112
WIP: ⚠️ Remove Metal3Machine owner reference from BMH #2506
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
base: main
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold |
/test metal3-centos-e2e-integration-test-main |
1 similar comment
/test metal3-centos-e2e-integration-test-main |
4def180
to
e92061b
Compare
/test metal3-centos-e2e-integration-test-main |
/test metal3-ubuntu-e2e-integration-test-main |
/test metal3-centos-e2e-integration-test-main |
/hold |
/hold cancel |
/hold |
/test metal3-ubuntu-e2e-integration-test-main |
/test metal3-centos-e2e-integration-test-main |
Run 2: Failed but unrelated IPA download issue https://jenkins.nordix.org/view/Metal3/job/metal3-centos-e2e-integration-test-main/1154/consoleFull |
/test metal3-centos-e2e-integration-test-main metal3-ubuntu-e2e-integration-test-main |
e92061b
to
1a836b0
Compare
/test metal3-centos-e2e-integration-test-main metal3-ubuntu-e2e-integration-test-main |
1a836b0
to
74bbadf
Compare
/test metal3-centos-e2e-integration-test-main metal3-ubuntu-e2e-integration-test-main |
74bbadf
to
24a8ff0
Compare
/test metal3-centos-e2e-integration-test-main metal3-ubuntu-e2e-integration-test-main |
/test metal3-centos-e2e-integration-test-main |
8 similar comments
/test metal3-centos-e2e-integration-test-main |
/test metal3-centos-e2e-integration-test-main |
/test metal3-centos-e2e-integration-test-main |
/test metal3-centos-e2e-integration-test-main |
/test metal3-centos-e2e-integration-test-main |
/test metal3-centos-e2e-integration-test-main |
/test metal3-centos-e2e-integration-test-main |
/test metal3-centos-e2e-integration-test-main |
/test metal3-centos-e2e-integration-test-main |
1 similar comment
/test metal3-centos-e2e-integration-test-main |
/test metal3-centos-e2e-integration-test-main |
5 similar comments
/test metal3-centos-e2e-integration-test-main |
/test metal3-centos-e2e-integration-test-main |
/test metal3-centos-e2e-integration-test-main |
/test metal3-centos-e2e-integration-test-main |
/test metal3-centos-e2e-integration-test-main |
Metal3Machine should not own BMH. It should consume it and release it when not needed. we already put a M3M consumer reference on BMH. This also would mean that for pivoting use cases we must add the clusterctl move labels in the CRDs. Otherwise BMH wont be pivoted to target clusters.⚠️ Now, BMH object/CRD needs to have The object has the clusterctl.cluster.x-k8s.io/move label or the clusterctl.cluster.x-k8s.io/move-hierarchy label to make sure BMH is pivoted to target cluster and removed from the source. clusterctl.cluster.x-k8s.io/move and clusterctl.cluster.x-k8s.io/move-hierarchy labels could be applied to single objects or at the CRD level (the label applies to all the objects). We still keep the removal of owner reference code for one minor release cycle to facilitate upgrade scenario where a BMH could still have an owner reference set from previous version. Starting from v1.11.x minor cycle we will remove this code also. Signed-off-by: Kashif Khan <kashif.khan@est.tech>
Signed-off-by: Kashif Khan <kashif.khan@est.tech>
Signed-off-by: Kashif Khan <kashif.khan@est.tech>
Signed-off-by: Kashif Khan <kashif.khan@est.tech>
8cd858b
to
7e055ce
Compare
/test metal3-centos-e2e-integration-test-main |
1 similar comment
/test metal3-centos-e2e-integration-test-main |
@kashifest: The following test failed, say
Instructions 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-sigs/prow repository. I understand the commands that are listed here. |
@kashifest: The following test failed, say
Full PR test history. Your PR dashboard. Instructions 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-sigs/prow repository. I understand the commands that are listed here. |
PR needs rebase. Instructions 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-sigs/prow repository. |
Metal3Machine should not own BMH. It should consume it and release it when not needed. we already put a M3M consumer reference on BMH. This also would mean that for pivoting use cases we must add the clusterctl move labels in the CRDs. Otherwise BMH wont be pivoted to target clusters.
We still keep the removal of owner reference code for one minor release cycle to facilitate upgrade scenario where a BMH could still have an owner reference set from previous version. Starting from v1.11.x minor cycle we will remove this code also.
Signed-off-by: Kashif Khan kashif.khan@est.tech