METAL-1404: Make baremetal capability disabled by default on hosted clusters

[MahnoorAsghar]

Make baremetal capability disabled by default on hosted clusters

Fixes #METAL-1404

[openshift-ci-robot]

@MahnoorAsghar: This pull request references METAL-1404 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.20.0" version, but no target version was set.

In response to this:

Make baremetal capability disabled by default on hosted clusters

Fixes #METAL-1404: https://issues.redhat.com/browse/METAL-1404

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@MahnoorAsghar: This pull request references METAL-1404 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.20.0" version, but no target version was set.

In response to this:

Make baremetal capability disabled by default on hosted clusters

Fixes #METAL-1404

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: MahnoorAsghar
Once this PR has been reviewed and has the lgtm label, please assign sjenning for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[MahnoorAsghar]

/jira refresh

[openshift-ci-robot]

@MahnoorAsghar: This pull request references METAL-1404 which is a valid jira issue.

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

[cwbotbot]

Test Results

e2e-aws

• Status: ✅ PASS
• Started: 2025-05-21T12:39:25Z
• View Job
• View Job History

e2e-aks

• Status: ❌ FAIL
• Started: 2025-05-21T12:39:24Z
• View Job
• View Job History

Failed Tests

Total failed tests: 5

• TestNodePool
• TestNodePool/HostedCluster0
• TestNodePool/HostedCluster0/Main
• TestNodePool/HostedCluster0/Main/TestNodePoolInPlaceUpgrade
• TestNodePool/HostedCluster0/Main/TestNodepoolMachineconfigGetsRolledout

[enxebre]

Thanks @MahnoorAsghar! To reduce impact over already persisted resources and preserve control over defaults, baremetal will be disabled by default unless explicitly included in "enabled", but it doesn't need to be explicitly included in the "disabled". Let's close this PR and put a new one for the explicit opt-in implementation

[openshift-ci]

@MahnoorAsghar: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aks	6d31c47	link	true	/test e2e-aks
ci/prow/verify-deps	6d31c47	link	true	/test verify-deps
ci/prow/unit	6d31c47	link	true	/test unit
ci/prow/verify	6d31c47	link	true	/test verify

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.