Skip to content

[cert-manager-1.20] OCPBUGS-85579: Move Console resources from bundle to runtime with capability detection - #467

Open
openshift-cherrypick-robot wants to merge 1 commit into
openshift:cert-manager-1.20from
openshift-cherrypick-robot:cherry-pick-455-to-cert-manager-1.20
Open

[cert-manager-1.20] OCPBUGS-85579: Move Console resources from bundle to runtime with capability detection#467
openshift-cherrypick-robot wants to merge 1 commit into
openshift:cert-manager-1.20from
openshift-cherrypick-robot:cherry-pick-455-to-cert-manager-1.20

Conversation

@openshift-cherrypick-robot

@openshift-cherrypick-robot openshift-cherrypick-robot commented Aug 4, 2026

Copy link
Copy Markdown

This is an automated cherry-pick of #455

/assign bharath-b-rh

@sebrandon1 @openshift-cherrypick-robot
OCPBUGS-85579: Move Console resources from bundle to runtime with CRD…
cf7eb2d 
… discovery

Move Console resource creation (ConsoleYAMLSample, ConsoleQuickStart) from the
OLM bundle to operator runtime, fixing installs on consoleless clusters where
OLM fails with "GroupVersionKind console.openshift.io/v1 not found".

At startup, the operator uses ResourceDiscoverer to check if Console CRDs exist.
If present, the console resources controller is created and applies resources
using the typed console clientset. If absent (MicroShift, consoleless RAN/SNO),
the controller is never started. Day-2 console enablement is picked up on
operator restart.

Key changes:
- Use typed consoleclient.Interface instead of dynamic.Interface
- CRD existence discovery at startup via utils.NewResourceDiscoverer
- Console controller conditionally created in CertManagerControllerSet
- Remove ClusterVersion capability polling (no more per-sync API calls)
- Remove clusterversions RBAC (no longer needed)
- Console assets loaded via generic loadAssets[T] with sigs.k8s.io/yaml
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Aug 4, 2026
Merged
@openshift-ci-robot

openshift-ci-robot commented Aug 4, 2026

Copy link
Copy Markdown

@openshift-cherrypick-robot: Could not make automatic cherrypick of Jira Issue OCPBUGS-85579 for this PR as the target version is not set for this branch in the jira plugin config. Running refresh:
/jira refresh

Details

In response to this:

This is an automated cherry-pick of #455

/assign bharath-b-rh

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.

@coderabbitai

coderabbitai Bot commented Aug 4, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

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: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: adc3a824-e9cf-4f1b-8cac-909e4672ef25

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

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

@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Aug 4, 2026
@openshift-ci-robot

openshift-ci-robot commented Aug 4, 2026

Copy link
Copy Markdown

@openshift-ci-robot: This pull request references Jira Issue OCPBUGS-85579, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED instead
  • expected Jira Issue OCPBUGS-85579 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

@openshift-cherrypick-robot: Could not make automatic cherrypick of Jira Issue OCPBUGS-85579 for this PR as the target version is not set for this branch in the jira plugin config. Running refresh:
/jira refresh

In response to this:

This is an automated cherry-pick of #455

/assign bharath-b-rh

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.

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 openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Aug 4, 2026
@bharath-b-rh

bharath-b-rh commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

This is an automated cherrypick PR, hence adding all the required labels
/lgtm
/approve
/label px-approved
/label docs-approved
/label qe-approved

@openshift-ci openshift-ci Bot added px-approved Signifies that Product Support has signed off on this PR docs-approved Signifies that Docs has signed off on this PR qe-approved Signifies that QE has signed off on this PR lgtm Indicates that a PR is ready to be merged. labels Aug 4, 2026
@openshift-ci

openshift-ci Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bharath-b-rh, openshift-cherrypick-robot

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

The pull request process is described 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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 4, 2026
@openshift-ci

openshift-ci Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: 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.

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

Reviewers

@bharath-b-rh bharath-b-rh Awaiting requested review from bharath-b-rh
@mytreya-rh mytreya-rh Awaiting requested review from mytreya-rh

Assignees

@bharath-b-rh bharath-b-rh

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. docs-approved Signifies that Docs has signed off on this PR jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@openshift-cherrypick-robot @openshift-ci-robot @bharath-b-rh @sebrandon1