🌱 Update policy version to v0.17.0

[JustinKuli]

Summary

This updates the 1.1.1 bundle to deploy policy components v0.17.0. This update does not require any other changes to hub resources, it just updates the image versions. Details on the changes can be found in these component release notes:

• config-policy-controller v0.17.0
• governance-policy-addon-controller v0.17.0
• governance-policy-framework-addon v0.17.0
• governance-policy-propagator v0.17.0

Summary by CodeRabbit

• Chores
  • Updated PolicyAddon to v0.17.0 for version 1.1.1. Other components remain at their current versions.

[coderabbitai]

Walkthrough

Updated the PolicyAddon version from v0.16.0 to v0.17.0 in the version 1.1.1 bundle. Other version components (OCM, AppAddon, MulticlusterControlplane) remain unchanged. This affects version resolution for the 1.1.1 release.

Changes

Cohort / File(s)	Change Summary
Version bundle update pkg/version/version.go	Bumped PolicyAddon from v0.16.0 to v0.17.0 in the 1.1.1 version bundle

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Simple, isolated version constant update with no logic changes or API modifications

Possibly related PRs

• clusteradm#514: Adds/updates the 1.1.0 version bundle in the same versionBundleList mapping
• clusteradm#517: Sets the default version to 1.1.1 in the same version configuration file

Suggested labels

approved, lgtm

Suggested reviewers

• TylerGillson
• ycyaoxdu

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically identifies the main change: updating the policy addon version to v0.17.0, which matches the sole modification in the changeset.
Description check	✅ Passed	The description includes the required Summary section with detailed context and linked component release notes. However, the 'Related issue(s)' section is missing, which is specified in the template.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bd289ee and 0b47818.

📒 Files selected for processing (1)

• pkg/version/version.go (1 hunks)

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: zhiweiyin318
Repo: open-cluster-management-io/clusteradm PR: 516
File: go.mod:34-34
Timestamp: 2025-11-05T15:25:15.187Z
Learning: In the clusteradm repository, the dependency upgrade of open-cluster-management.io/ocm to v1.1.1-0.20251105064423-d80ec55608e7 is intentional and required to support the gRPC registration feature being added.

📚 Learning: 2025-11-05T15:25:15.187Z

Learnt from: zhiweiyin318
Repo: open-cluster-management-io/clusteradm PR: 516
File: go.mod:34-34
Timestamp: 2025-11-05T15:25:15.187Z
Learning: In the clusteradm repository, the dependency upgrade of open-cluster-management.io/ocm to v1.1.1-0.20251105064423-d80ec55608e7 is intentional and required to support the gRPC registration feature being added.

Applied to files:

• pkg/version/version.go

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: e2e-test
• GitHub Check: verify
• GitHub Check: unit-test

🔇 Additional comments (1)

pkg/version/version.go (1)

109-114: PolicyAddon v0.17.0 update verified and approved.

All policy component releases (config-policy-controller, governance-policy-addon-controller, governance-policy-framework-addon, and governance-policy-propagator) have v0.17.0 available. The change correctly updates PolicyAddon in the 1.1.1 default bundle to v0.17.0, aligning with the PR objectives.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining why this PR is needed, why this solution was chosen, and what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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 and usage tips.}

[mikeshng]

/lgtm

[zhujian7]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JustinKuli, mikeshng, zhujian7

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [zhujian7]

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