feat(base-cluster/kyverno): add capability for exceptions to be in all namespaces

[tasches]

Summary by CodeRabbit

• New Features
  • Added support for a wildcard namespace in Kyverno policy exceptions, enabling cluster-wide applicability.
  • Simplifies configuration by allowing policy exceptions to apply across all namespaces when enabled.

[coderabbitai]

Walkthrough

Added a namespace wildcard to Kyverno policyExceptions in the HelmRelease values by introducing policyExceptions.namespace: '*' while keeping policyExceptions.enabled: true unchanged.

Changes

Cohort / File(s)	Summary
Kyverno HelmRelease config charts/base-cluster/templates/kyverno/kyverno.yaml	Added policyExceptions.namespace: '*' under Kyverno HelmRelease values; no other keys modified.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I twitch my ears at YAML stars,
Asterisk skies in cluster jars—
Kyverno nods, “Exceptions roam,”
Wildcard paths through namespace foam.
I stamp, I hop—config is bright,
Carrots aligned, releases right.

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/kyverno-namespaces

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

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

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

charts/base-cluster/templates/kyverno/kyverno.yaml (1)

61-61: YAML asterisk is safely quoted; keep it that way

Using single quotes prevents YAML alias expansion of *. If you later switch to a templated value, ensure you still apply | quote to avoid unintentional alias parsing or invalid YAML when the value contains special characters.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 93ae5fc and ef1ede2.

📒 Files selected for processing (1)

• charts/base-cluster/templates/kyverno/kyverno.yaml (1 hunks)

⏰ 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). (2)

• GitHub Check: check licenses
• GitHub Check: lint helm chart (base-cluster)

🔇 Additional comments (1)

charts/base-cluster/templates/kyverno/kyverno.yaml (1)

59-62: policyExceptions.namespace="*" — wildcard support confirmed

Confirmed: the Kyverno chart and upstream docs support setting features.policyExceptions.namespace to "*" to accept PolicyExceptions from all namespaces. The repo template already sets this.

Files to note:

• charts/base-cluster/templates/kyverno/kyverno.yaml — features.policyExceptions.enabled: true and namespace: '*' (around lines 59–61)

Actionable recommendations (advisory):

• Ensure RBAC prevents untrusted principals from creating PolicyException objects.
• Optionally make the namespace configurable so deployments can opt out without editing the template.

Suggested optional diff:

-        namespace: '*'
+        namespace: {{ default "*" (index .Values "kyverno" "policyExceptions" "namespace") | quote }}