Skip to content

[cert-manager-1.19] OCPBUGS-104580: Move Console resources from bundle to runtime with capability detection - #468

Merged
openshift-merge-bot[bot] merged 4 commits into
openshift:cert-manager-1.19from
bharath-b-rh:cert-manager-1.19
Aug 6, 2026
Merged

[cert-manager-1.19] OCPBUGS-104580: Move Console resources from bundle to runtime with capability detection#468
openshift-merge-bot[bot] merged 4 commits into
openshift:cert-manager-1.19from
bharath-b-rh:cert-manager-1.19

Conversation

@bharath-b-rh

Copy link
Copy Markdown
Contributor

This is a manual cherry-pick of #455

/assign @mytreya-rh

… 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-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. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 5, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@bharath-b-rh: 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 Release Pending (Done) 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:

This is a manual cherry-pick of #455

/assign @mytreya-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 5, 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: 40a4643c-e47a-4f25-9957-16847b76a014

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 openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 5, 2026
@bharath-b-rh bharath-b-rh changed the title OCPBUGS-85579: Move Console resources from bundle to runtime with CRD discovery [cert-manager-1.19] OCPBUGS-104580: Move Console resources from bundle to runtime with capability detection Aug 5, 2026
@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 5, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@bharath-b-rh: This pull request references Jira Issue OCPBUGS-104580, which is valid. The bug has been moved to the POST state.

5 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-85579 is in the state Release Pending (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (amendiol@redhat.com), skipping review request.

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

Details

In response to this:

This is a manual cherry-pick of #455

/assign @mytreya-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.

@bharath-b-rh

Copy link
Copy Markdown
Contributor Author

This is a cherrypick, hence adding the below labels
/approve
/label docs-approved
/label px-approved
/label qe-approved

@openshift-ci openshift-ci Bot added docs-approved Signifies that Docs has signed off on this PR px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR labels Aug 5, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@bharath-b-rh: This pull request references Jira Issue OCPBUGS-104580, which is valid.

5 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-85579 is in the state Release Pending (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (amendiol@redhat.com), skipping review request.

Details

In response to this:

This is a manual cherry-pick of #455

/assign @mytreya-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.

@bharath-b-rh

Copy link
Copy Markdown
Contributor Author

/test e2e-operator-tech-preview

Arun Maurya and others added 3 commits August 5, 2026 19:11
The vault-installer pod was rejected on clusters enforcing Pod Security
restricted:latest because it ran with privileged=true. Helm install only
needs API access via the service account, so use a restricted-compliant
security context instead.

Co-authored-by: Cursor <cursoragent@cursor.com>
Signed-off-by: Bharath B <bhb@redhat.com>
@openshift-ci

openshift-ci Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

@bharath-b-rh: 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.

@mytreya-rh

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 6, 2026
@openshift-ci

openshift-ci Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bharath-b-rh, mytreya-rh

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:
  • OWNERS [bharath-b-rh,mytreya-rh]

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

@openshift-merge-bot
openshift-merge-bot Bot merged commit 6289161 into openshift:cert-manager-1.19 Aug 6, 2026
13 checks passed
@openshift-ci-robot

Copy link
Copy Markdown

@bharath-b-rh: Jira Issue OCPBUGS-104580: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-104580 has been moved to the MODIFIED state.

Details

In response to this:

This is a manual cherry-pick of #455

/assign @mytreya-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.

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

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/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid 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

Development

Successfully merging this pull request may close these issues.

4 participants