OCPCLOUD-3319: Remove capiinstaller controller

[mdbooth]

Removes the legacy capiinstaller controller, which still handles transport configmaps. Only ORC that we know of is still using these.

TODO:

• Merge OCPCLOUD-3319: Create installer controller #494
• OSASINFRA-3980, OCPCLOUD-3321: Add openstack-resource-controller image to images.json #506
• OSASINFRA-3980, OCPCLOUD-3321: Update to image-based manifests openstack-resource-controller#30

[openshift-ci-robot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci-robot]

@mdbooth: This pull request references OCPCLOUD-3319 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.22.0" version, but no target version was set.

Details

In response to this:

Requires the new installer to merge first: #494

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]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[coderabbitai]

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Excluded labels (none allowed) (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: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: b947f756-7776-47a7-9eb0-116de6e3f95c

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

---

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign theobarberbany 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:

• OWNERS

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

[openshift-ci-robot]

@mdbooth: This pull request references OCPCLOUD-3319 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.22.0" version, but no target version was set.

Details

In response to this:

Requires the new installer to merge first: #494

TODO:

• Merge OCPCLOUD-3319: Create installer controller #494

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]

@mdbooth: This pull request references OCPCLOUD-3319 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.22.0" version, but no target version was set.

Details

In response to this:

Requires the new installer to merge first: #494

TODO:

• Merge OCPCLOUD-3319: Create installer controller #494

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]

@mdbooth: This pull request references OCPCLOUD-3319 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.22.0" version, but no target version was set.

Details

In response to this:

Requires the new installer to merge first: #494

TODO:

• Merge OCPCLOUD-3319: Create installer controller #494
• OSASINFRA-3980, OCPCLOUD-3321: Add openstack-resource-controller image to images.json #506
• OSASINFRA-3980, OCPCLOUD-3321: Update to image-based manifests openstack-resource-controller#30

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]

@mdbooth: This pull request references OCPCLOUD-3319 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.22.0" version, but no target version was set.

Details

In response to this:

Removes the legacy capiinstaller controller, which still handles transport configmaps. Only ORC that we know of is still using these.

TODO:

• Merge OCPCLOUD-3319: Create installer controller #494
• OSASINFRA-3980, OCPCLOUD-3321: Add openstack-resource-controller image to images.json #506
• OSASINFRA-3980, OCPCLOUD-3321: Update to image-based manifests openstack-resource-controller#30

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]

@mdbooth: This pull request references OCPCLOUD-3319 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.22.0" version, but no target version was set.

Details

In response to this:

Removes the legacy capiinstaller controller, which still handles transport configmaps. Only ORC that we know of is still using these.

TODO:

• Merge OCPCLOUD-3319: Create installer controller #494
• OSASINFRA-3980, OCPCLOUD-3321: Add openstack-resource-controller image to images.json #506
• OSASINFRA-3980, OCPCLOUD-3321: Update to image-based manifests openstack-resource-controller#30

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]

@mdbooth: This pull request references OCPCLOUD-3319 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.22.0" version, but no target version was set.

Details

In response to this:

Removes the legacy capiinstaller controller, which still handles transport configmaps. Only ORC that we know of is still using these.

TODO:

• Merge OCPCLOUD-3319: Create installer controller #494
• OSASINFRA-3980, OCPCLOUD-3321: Add openstack-resource-controller image to images.json #506
• OSASINFRA-3980, OCPCLOUD-3321: Update to image-based manifests openstack-resource-controller#30

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]

@mdbooth: all tests passed!

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.