Skip to content

WIP: Use IrSO to deploy Ironic#523

Open
alegacy wants to merge 1 commit intoopenshift:mainfrom
alegacy:feature/deploy-ironic-with-irso
Open

WIP: Use IrSO to deploy Ironic#523
alegacy wants to merge 1 commit intoopenshift:mainfrom
alegacy:feature/deploy-ironic-with-irso

Conversation

@alegacy
Copy link
Copy Markdown
Contributor

@alegacy alegacy commented Nov 6, 2025

Refactor CBO to use the Ironic Standalone Operator (IrSO) for managing the Ironic deployment instead of directly creating and managing the metal3 pod.

Key changes:

  • Add new provisioning/ironic_deployment.go to create and manage Ironic CR
  • Update controller to manage Ironic CR instead of metal3 deployment
  • Remove metal3 state service (now handled by IrSO)
  • Add RBAC permissions for ironic.metal3.io resources
  • Update deployment state checking to use IrSO-managed deployment
  • Refactor baremetal_pod.go to work with IrSO-created resources

This change delegates Ironic deployment management to IrSO while CBO continues to manage the overall provisioning configuration and BMO.

🤖 Generated with Claude Code

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 6, 2025
@alegacy
Copy link
Copy Markdown
Contributor Author

alegacy commented Nov 6, 2025

cc @dtantsur


func EnsureAllSecrets(info *ProvisioningInfo) (bool, error) {
// Create a Secret for the Ironic Password
// TODO(alegacy): Ironic will do this on its own if we don't create one. Maybe we should retrieve it instead?
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume creating it here, is better than letter IrSO do it.

}
imageName := path.Base(fileCompressionSuffix.ReplaceAllString(downloadURL.Path, ""))

// TODO(alegacy): not sure what needs to happen with the following block
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not 100% sure how this is used or if it needs to change for IrSO.

@openshift-ci openshift-ci bot requested review from dtantsur and zaneb November 6, 2025 14:15
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Nov 6, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details 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

spec := ironicv1alpha1.IronicSpec{
APICredentialsName: ironicAPICredentialsName,
TLS: ironicv1alpha1.TLS{
CertificateName: tlsSecretName,
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Set trusted CA when metal3-io/ironic-standalone-operator#420 merges.

@alegacy
Copy link
Copy Markdown
Contributor Author

alegacy commented Nov 6, 2025

Open action items:

  1. How to deploy IrSO operator
  2. How to deal with upgrades
  3. Pass through for IPE config options to Ironic CR

networking.DHCP = dhcp
}
}

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You'll need to use Overrides to inject OpenShift-specific containers (static IP stuff).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, i'll put that back in. Sorry, got a little too quick on the delete key.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've added them back in including the machine-os containers.

Refactor CBO to use the Ironic Standalone Operator (IrSO) for managing
the Ironic deployment instead of directly creating and managing the
metal3 pod.

Key changes:
- Add new provisioning/ironic_deployment.go to create and manage Ironic CR
- Update controller to manage Ironic CR instead of metal3 deployment
- Remove metal3 state service (now handled by IrSO)
- Add RBAC permissions for ironic.metal3.io resources
- Update deployment state checking to use IrSO-managed deployment
- Refactor baremetal_pod.go to work with IrSO-created resources

This change delegates Ironic deployment management to IrSO while CBO
continues to manage the overall provisioning configuration and BMO.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
Signed-off-by: Allain Legacy <alegacy@redhat.com>
@alegacy alegacy force-pushed the feature/deploy-ironic-with-irso branch from 35c385a to ef0cb45 Compare November 8, 2025 13:04
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 8, 2025
@openshift-merge-robot
Copy link
Copy Markdown
Contributor

PR needs rebase.

Details

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.

@alegacy
Copy link
Copy Markdown
Contributor Author

alegacy commented Nov 8, 2025

@dtantsur The pending rebase has the prometheus rules. ... is that going to be ported to IrSO along with the service monitor?

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Nov 17, 2025

@alegacy: 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/gofmt ef0cb45 link true /test gofmt
ci/prow/e2e-metal-ipi-bm ef0cb45 link true /test e2e-metal-ipi-bm
ci/prow/unit ef0cb45 link true /test unit
ci/prow/govet ef0cb45 link true /test govet
ci/prow/verify-deps ef0cb45 link true /test verify-deps
ci/prow/e2e-agnostic-ovn ef0cb45 link true /test e2e-agnostic-ovn
ci/prow/okd-scos-images ef0cb45 link true /test okd-scos-images
ci/prow/e2e-metal-ipi-serial-ipv4 ef0cb45 link true /test e2e-metal-ipi-serial-ipv4
ci/prow/images ef0cb45 link true /test images
ci/prow/generate-check ef0cb45 link true /test generate-check
ci/prow/okd-scos-e2e-aws-ovn ef0cb45 link false /test okd-scos-e2e-aws-ovn
ci/prow/lint ef0cb45 link true /test lint
ci/prow/e2e-metal-ipi-ovn-ipv6 ef0cb45 link true /test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-hypershift ef0cb45 link true /test e2e-hypershift

Full PR test history. Your PR dashboard.

Details

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.

@openshift-bot
Copy link
Copy Markdown

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 16, 2026
@openshift-bot
Copy link
Copy Markdown

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 18, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 18, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9ff264e9-25da-48ba-a3df-6ecf8d47d79e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
📝 Coding Plan
  • Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants