Skip to content

Conversation

@arun717
Copy link
Contributor

@arun717 arun717 commented Jan 6, 2026

Rebase istio-csr with upstream v0.15.0

Steps followed:
Made use of the update script in this PR: #309
Modified the script to handle istio-csr updates.
The new script changes will be pushed as part of the original PR: #309

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 6, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 6, 2026

@arun717: This pull request references CM-826 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:

Rebase istio-csr with upstream v0.15.0

Steps followed:
Made use of the update script in this PR: #309
Modified the script to handle istio-csr updates.
The new script changes will be pushed as part of the original PR: #309

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
Copy link

coderabbitai bot commented Jan 6, 2026

Walkthrough

This pull request bumps cert-manager-istio-csr from v0.14.2 to v0.15.0 across build files, Kubernetes manifests, operator CSV, manager config, and embedded asset manifests. No control-flow or API declaration changes.

Changes

Cohort / File(s) Summary
Istio CSR Manifests
bindata/istio-csr/cert-manager-istio-csr-clusterrole.yaml, bindata/istio-csr/cert-manager-istio-csr-clusterrolebinding.yaml, bindata/istio-csr/cert-manager-istio-csr-leases-role.yaml, bindata/istio-csr/cert-manager-istio-csr-leases-rolebinding.yaml, bindata/istio-csr/cert-manager-istio-csr-role.yaml, bindata/istio-csr/cert-manager-istio-csr-rolebinding.yaml, bindata/istio-csr/cert-manager-istio-csr-metrics-service.yaml, bindata/istio-csr/cert-manager-istio-csr-service.yaml, bindata/istio-csr/cert-manager-istio-csr-serviceaccount.yaml, bindata/istio-csr/istiod-certificate.yaml
Updated metadata.labels.app.kubernetes.io/version values from v0.14.2 to v0.15.0.
Istio CSR Deployment
bindata/istio-csr/cert-manager-istio-csr-deployment.yaml
Updated deployment labels and container image from v0.14.2 to v0.15.0 (quay.io/jetstack/cert-manager-istio-csr).
Operator CSV & Config
bundle/manifests/cert-manager-operator.clusterserviceversion.yaml, config/manager/manager.yaml
Updated RELATED_IMAGE, ISTIOCSR_OPERAND_IMAGE_VERSION, relatedImages entries and deployment image tags to v0.15.0.
Build and Embedded Assets
Makefile, pkg/operator/assets/bindata.go
Bumped ISTIO_CSR_VERSION variable and updated embedded manifest content/image tags to v0.15.0.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes


📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to Reviews -> Disable Knowledge Base setting

📥 Commits

Reviewing files that changed from the base of the PR and between ca3d048 and c7e603c.

📒 Files selected for processing (1)
  • config/manager/manager.yaml
🚧 Files skipped from review as they are similar to previous changes (1)
  • config/manager/manager.yaml

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

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 4

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
config/manager/manager.yaml (1)

86-90: Update ISTIOCSR_OPERAND_IMAGE_VERSION to match the image tag.

The RELATED_IMAGE_CERT_MANAGER_ISTIOCSR was updated to v0.15.0, but ISTIOCSR_OPERAND_IMAGE_VERSION is still 0.14.2. This variable is used to set the app.kubernetes.io/version label on deployed resources, creating an inconsistency between the actual deployed image version and what the operator reports. Update ISTIOCSR_OPERAND_IMAGE_VERSION to 0.15.0.

🤖 Fix all issues with AI Agents
In @bundle/manifests/cert-manager-operator.clusterserviceversion.yaml:
- Line 827: The CSV's replaces field currently points to
"cert-manager-operator.v1.18.0" which matches the current CSV version (v1.18.0)
and thus incorrectly indicates self-replacement; update the replaces value to
the previous release (e.g., "cert-manager-operator.v1.17.0") so the replaces
field refers to the prior CSV instead of the current one, ensuring the CSV's
replaces metadata is correct.
- Line 253: The olm.skipRange annotation currently reads '>=1.18.0 <1.18.0',
which is impossible to satisfy; update the value for the olm.skipRange
annotation (the key "olm.skipRange" in the manifest) to a valid range such as
'>=1.17.0 <1.18.0' or, if you intended to skip 1.18.x, '>=1.18.0 <1.19.0' so OLM
upgrade logic works correctly.

In @config/manifests/bases/cert-manager-operator.clusterserviceversion.yaml:
- Line 21: The olm.skipRange value is logically empty (">=1.18.0 <1.18.0");
update the skipRange on the ClusterServiceVersion metadata to a valid semver
range that allows upgrades from the previous minor (e.g., change the
olm.skipRange expression to ">=1.17.0 <1.18.0") so OLM upgrade semantics work
correctly; locate the olm.skipRange entry in the cert-manager-operator CSV and
replace the existing string accordingly.
- Line 152: The replaces field currently points to the same version causing a
circular OLM reference; update the replaces value in the ClusterServiceVersion
manifest (the replaces: entry) from "cert-manager-operator.v1.18.0" to the
previous release "cert-manager-operator.v1.17.0" so the CSV correctly declares
it replaces the prior version instead of itself.
📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to Reviews -> Disable Knowledge Base setting

📥 Commits

Reviewing files that changed from the base of the PR and between b0b1af8 and e132a87.

📒 Files selected for processing (16)
  • Makefile
  • bindata/istio-csr/cert-manager-istio-csr-clusterrole.yaml
  • bindata/istio-csr/cert-manager-istio-csr-clusterrolebinding.yaml
  • bindata/istio-csr/cert-manager-istio-csr-deployment.yaml
  • bindata/istio-csr/cert-manager-istio-csr-leases-role.yaml
  • bindata/istio-csr/cert-manager-istio-csr-leases-rolebinding.yaml
  • bindata/istio-csr/cert-manager-istio-csr-metrics-service.yaml
  • bindata/istio-csr/cert-manager-istio-csr-role.yaml
  • bindata/istio-csr/cert-manager-istio-csr-rolebinding.yaml
  • bindata/istio-csr/cert-manager-istio-csr-service.yaml
  • bindata/istio-csr/cert-manager-istio-csr-serviceaccount.yaml
  • bindata/istio-csr/istiod-certificate.yaml
  • bundle/manifests/cert-manager-operator.clusterserviceversion.yaml
  • config/manager/manager.yaml
  • config/manifests/bases/cert-manager-operator.clusterserviceversion.yaml
  • pkg/operator/assets/bindata.go
🧰 Additional context used
📓 Path-based instructions (1)
**

⚙️ CodeRabbit configuration file

-Focus on major issues impacting performance, readability, maintainability and security. Avoid nitpicks and avoid verbosity.

Files:

  • Makefile
  • bindata/istio-csr/cert-manager-istio-csr-service.yaml
  • bindata/istio-csr/cert-manager-istio-csr-deployment.yaml
  • bindata/istio-csr/istiod-certificate.yaml
  • bindata/istio-csr/cert-manager-istio-csr-serviceaccount.yaml
  • bindata/istio-csr/cert-manager-istio-csr-metrics-service.yaml
  • bindata/istio-csr/cert-manager-istio-csr-clusterrole.yaml
  • config/manifests/bases/cert-manager-operator.clusterserviceversion.yaml
  • bindata/istio-csr/cert-manager-istio-csr-clusterrolebinding.yaml
  • bundle/manifests/cert-manager-operator.clusterserviceversion.yaml
  • config/manager/manager.yaml
  • bindata/istio-csr/cert-manager-istio-csr-leases-rolebinding.yaml
  • pkg/operator/assets/bindata.go
  • bindata/istio-csr/cert-manager-istio-csr-leases-role.yaml
  • bindata/istio-csr/cert-manager-istio-csr-role.yaml
  • bindata/istio-csr/cert-manager-istio-csr-rolebinding.yaml
🔇 Additional comments (15)
Makefile (1)

8-8: LGTM!

The version bump from v0.14.2 to v0.15.0 is correctly applied and aligns with the PR objective to rebase istio-csr to upstream v0.15.0.

bundle/manifests/cert-manager-operator.clusterserviceversion.yaml (2)

709-709: LGTM!

The istio-csr image reference is correctly updated to v0.15.0, consistent with the version bump throughout the PR.


825-826: LGTM!

The relatedImages entry is correctly updated to v0.15.0, maintaining consistency with the environment variable reference.

bindata/istio-csr/cert-manager-istio-csr-service.yaml (1)

10-10: LGTM!

The version label is correctly updated to v0.15.0, maintaining consistency across istio-csr manifests.

bindata/istio-csr/istiod-certificate.yaml (1)

9-9: LGTM!

The version label is correctly updated to v0.15.0, consistent with the istio-csr version bump across all manifests.

bindata/istio-csr/cert-manager-istio-csr-metrics-service.yaml (1)

10-10: LGTM!

The version label is correctly updated to v0.15.0, maintaining consistency with other istio-csr Service manifests.

bindata/istio-csr/cert-manager-istio-csr-role.yaml (1)

7-7: LGTM! Version label correctly updated.

The version label update to v0.15.0 is consistent with the upstream rebase objective.

bindata/istio-csr/cert-manager-istio-csr-clusterrolebinding.yaml (1)

7-7: LGTM! Version label correctly updated.

The version label update to v0.15.0 aligns with the rebase to upstream v0.15.0.

bindata/istio-csr/cert-manager-istio-csr-leases-role.yaml (1)

7-7: LGTM! Version label correctly updated.

The version label update to v0.15.0 is consistent with the upstream rebase.

bindata/istio-csr/cert-manager-istio-csr-serviceaccount.yaml (1)

7-7: LGTM! Version label correctly updated.

The version label update to v0.15.0 aligns with the rebase objective.

bindata/istio-csr/cert-manager-istio-csr-leases-rolebinding.yaml (1)

9-9: LGTM! Version label correctly updated.

The version label update to v0.15.0 is consistent with the upstream rebase to v0.15.0.

bindata/istio-csr/cert-manager-istio-csr-clusterrole.yaml (1)

7-7: LGTM! Version label updated correctly.

The version label update from v0.14.2 to v0.15.0 aligns with the PR's objective to rebase istio-csr to upstream v0.15.0.

bindata/istio-csr/cert-manager-istio-csr-rolebinding.yaml (1)

9-9: LGTM! Version label correctly updated.

The version label update is consistent with the istio-csr v0.15.0 rebase.

bindata/istio-csr/cert-manager-istio-csr-deployment.yaml (1)

9-9: LGTM! Deployment version updated consistently.

The version label and container image references are all consistently updated to v0.15.0 across the Deployment metadata, pod template labels, and container image tag.

Also applies to: 22-22, 29-29

pkg/operator/assets/bindata.go (1)

2277-2277: LGTM! Consistent version updates to v0.15.0.

All istio-csr resource version labels and the container image tag have been consistently updated to v0.15.0. The changes are correctly applied across all related resources (ClusterRole, ClusterRoleBinding, Deployment, Roles, RoleBindings, Services, ServiceAccount, and Certificate).

Also applies to: 2328-2328, 2364-2364, 2377-2377, 2384-2384, 2463-2463, 2509-2509, 2545-2545, 2579-2579, 2626-2626, 2662-2662, 2696-2696, 2725-2725

Copy link
Member

@chiragkyal chiragkyal left a comment

Choose a reason for hiding this comment

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

Steps followed:
Made use of the update script in this PR: #309
Modified the script to handle istio-csr updates.
The new script changes will be pushed as part of the original PR: #309

I think Istio-CSR manifest update is fairly easier task since we have make targets for them as compared to the actual rebase, and can be done independently of the proposed rebase script. Do we have a good reason to couple them?

Copy link
Contributor

@bharath-b-rh bharath-b-rh left a comment

Choose a reason for hiding this comment

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

LGTM except for couple of nits.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 6, 2026
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 7, 2026
Copy link
Contributor

@bharath-b-rh bharath-b-rh left a comment

Choose a reason for hiding this comment

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

LGTM, could you check and fix the verify CI job. Once done, this is good to be merged.

@arun717 arun717 requested a review from chiragkyal January 8, 2026 06:32
Copy link
Member

@chiragkyal chiragkyal left a comment

Choose a reason for hiding this comment

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

Please squash/modify the commits a bit. We can have two commits: first with the changes made manually, and next with the changes made through make targets.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 8, 2026

@arun717: 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.

@bharath-b-rh
Copy link
Contributor

/label tide/merge-method-squash
/label px-approved
/label docs-approved

@openshift-ci openshift-ci bot added tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. px-approved Signifies that Product Support has signed off on this PR docs-approved Signifies that Docs has signed off on this PR labels Jan 8, 2026
Copy link
Member

@lunarwhite lunarwhite left a comment

Choose a reason for hiding this comment

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

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Jan 8, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 8, 2026

@arun717: This pull request references CM-826 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:

Rebase istio-csr with upstream v0.15.0

Steps followed:
Made use of the update script in this PR: #309
Modified the script to handle istio-csr updates.
The new script changes will be pushed as part of the original PR: #309

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
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 8, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 8, 2026

[APPROVALNOTIFIER] This PR is APPROVED

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

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 Jan 8, 2026
@openshift-merge-bot openshift-merge-bot bot merged commit da0c512 into openshift:master Jan 8, 2026
11 checks passed
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/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 tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants