CM-1222: z-stream 1.17.2 operator release with sustaining CVE backports

[sakshiep1]

Summary

Operator z-stream release 1.17.2 for CM-1222, with downstream openshift-sustaining CVE backports in operator go.mod and patched operand sources from jetstack.

Component	Version
Operator (OLM bundle)	1.17.2
Operand (cert-manager)	v1.17.4 (label unchanged; rebuilt with CVE fixes)

Jetstack dependency

openshift/jetstack-cert-manager#45 is merged.

• Merge commit: a9537101948b58e4c5e644916f65ffcbd9d86e49
• Operator go.mod replace updated to that commit (v1.17.5-0.20260824055811-a9537101948b)
• operand.Dockerfile updated to clone release-1.17 so CI operand image builds include the CVE fixes

Note: No v1.17.5 tag exists yet on jetstack. Using release-1.17 for operand builds until a tag is cut (same pattern as pinning v1.18.6 on the 1.18 line). Can switch to v1.17.5 once tagged.

Changes

Operator version bump (1.17.1 → 1.17.2)

• BUNDLE_VERSION → 1.17.2 in Makefile
• CSV: OLM bundle name, version, replaces, skipRange
• OPERATOR_IMAGE_VERSION in config/manager/manager.yaml

CVE fixes (operator go.mod)

CVE	Package	Fix
CVE-2026-33186	google.golang.org/grpc	replace → openshift-sustaining/grpc-go@v1.75.1-sec.1
CVE-2026-39821	golang.org/x/net/idna	replace → openshift-sustaining/net@v0.50.0-sec.2
CVE-2026-25681	golang.org/x/net/html	same net replace (cumulative)
CVE-2026-46597	golang.org/x/crypto/ssh	replace → openshift-sustaining/crypto@v0.48.0-sec.1
CVE-2026-34986	go-jose/v4	N/A on operator (fixed in jetstack #45 only)

Sustaining backports used instead of upstream minor bumps to remain compatible with Go 1.24 builder (rhel-9-golang-1.24-openshift-4.20).

Jetstack / operand build

• go.mod: jetstack replace → merge commit a953710… (post–Initial e2e tests #45)
• images/ci/operand.Dockerfile: RELEASE_BRANCH v1.17.4 → release-1.17

Commits

• CM-1222: bump BUNDLE_VERSION to 1.17.2
• CM-1222: update CSV OLM bundle name, version, replaces, skipRange
• CM-1222: update OPERATOR_IMAGE_VERSION references
• CM-1222: Apply openshift-sustaining CVE backports in operator go.mod
• CM-1222: Point jetstack replace to post-CVE merge commit

Verification

go mod tidy
go mod vendor
go build ./...
govulncheck ./...  # target CVE govulncheck entries cleared
make update-bindata
make bundle

[openshift-ci-robot]

@sakshiep1: This pull request references CM-1222 which is a valid jira issue.

Details

In response to this:

Summary

Operator z-stream release 1.17.2 for CM-1222, with downstream openshift-sustaining CVE backports in operator go.mod.

Component	Version
Operator (OLM bundle)	1.17.2
Operand (cert-manager)	v1.17.4 (unchanged)

Depends on

• openshift/jetstack-cert-manager#45 — operand CVE fixes on release-1.17

After #45 merges, this PR will be updated with the jetstack merge commit (or tag) in the go.mod replace directive before marking ready for review.

Changes

Operator version bump (1.17.1 → 1.17.2)

• BUNDLE_VERSION → 1.17.2 in Makefile
• CSV: OLM bundle name, version, replaces, skipRange
• OPERATOR_IMAGE_VERSION in config/manager/manager.yaml

CVE fixes (operator go.mod)

CVE	Package	Fix
CVE-2026-33186	google.golang.org/grpc	replace → openshift-sustaining/grpc-go@v1.75.1-sec.1
CVE-2026-39821	golang.org/x/net/idna	replace → openshift-sustaining/net@v0.50.0-sec.2
CVE-2026-25681	golang.org/x/net/html	same net replace (cumulative)
CVE-2026-46597	golang.org/x/crypto/ssh	replace → openshift-sustaining/crypto@v0.48.0-sec.1
CVE-2026-34986	go-jose/v4	N/A on operator (fixed in jetstack #45 only)

Sustaining backports used instead of upstream minor bumps to remain compatible with Go 1.24 builder (rhel-9-golang-1.24-openshift-4.20).

Commits

• CM-1222: bump BUNDLE_VERSION to 1.17.2
• CM-1222: update CSV OLM bundle name, version, replaces, skipRange
• CM-1222: update OPERATOR_IMAGE_VERSION references
• CM-1222: Apply openshift-sustaining CVE backports in operator go.mod

Verification

go mod tidy
go mod vendor
go build ./...
govulncheck ./...  # target CVE govulncheck entries cleared
make update-bindata
make bundle

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 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: Pro Plus

Run ID: 553b6e32-1889-496f-8976-242258d30b16

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

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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