[Svarrogh1337]

This pull request introduces comprehensive documentation and example updates to support fine-grained enforcement and mutation of Kubernetes Pod priority classes within Capsule. It adds detailed explanations, configuration examples, and migration guidance for priority class policies, and updates related sample manifests and references accordingly.

Major documentation additions and updates:

Priority class policy enforcement:

• Added an extensive new section on priority class enforcement to workloads.md, covering configuration, matching by name/regex/labels, audit/deny/allow actions, controller template handling, update behaviors, namespace profiles, and migration from legacy fields.
• Updated workload enforcement tables, targets, and reference examples to include priority class policies alongside existing resource, placement, and security policies. [1] [2] [3] [4] [5] [6] [7] [8] [9]

Mutation documentation:

• Documented how classes.priority can be assigned via mutation in merge/replace modes, and updated property tables to include classes. [1] [2]

Example and sample manifest updates:

Tenant resource and status examples:

• Updated example manifests and status blocks in global.md and tenant.md to remove legacy priority class fields and references, focusing on storage classes instead. [1] [2] [3]

Other related clarifications:

Update and enforcement behavior:

• Clarified in rules/_index.md that priority class enforcement is reevaluated on updates only when allow/deny rules have conditions.

[netlify]

✅ Deploy Preview for docs-projectcapsule ready!

Name	Link
🔨 Latest commit	b365d26
🔍 Latest deploy log	https://app.netlify.com/projects/docs-projectcapsule/deploys/6aed820eecf352e5860fb11b
😎 Deploy Preview	https://deploy-preview-182--docs-projectcapsule.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[Copilot]

🟡 Changes recommended

The release note incorrectly says existing generators receive no entries, but templates using missingKey: error can fail reconciliation when status.classes.priority is absent and need migration or a missing-key guard.

1 open issue

• Removing the field can break generators using missingKey: error · New

What changed in this PR

This documentation update explains namespace-specific PriorityClass enforcement and mutation in Capsule, including migration from legacy Tenant settings.

Changes:

• Documents PriorityClass matching, mutation, controller targets, and update behavior.
• Adds configuration examples and guidance for combining legacy settings with namespace rules.
• Updates release notes and replication examples for the removal of status.classes.priority.

File	Description
content/​en/​docs/​whats-new.md	Announces PriorityClass features and the status-field removal.
content/​en/​docs/​tenants/​enforcement.md	Links legacy settings to new rules and migration guidance.
content/​en/​docs/​rules/​mutate/​workloads.md	Documents PriorityClass assignment and merge/replace behavior.
content/​en/​docs/​rules/​mutate/​_index.md	Adds class mutation semantics to shared guidance.
content/​en/​docs/​rules/​enforcement/​workloads.md	Adds PriorityClass enforcement, targeting, and migration examples.
content/​en/​docs/​rules/​_index.md	Clarifies conditional PriorityClass checks on updates.
content/​en/​docs/​replications/​tenant.md	Removes the obsolete priority-class status example.
content/​en/​docs/​replications/​global.md	Switches generated RBAC examples to storage classes and updates status.

_{Review effort: Balanced}