An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
Your reproduction indicates that the required exclusion is absent when the validating policy evaluates the request. However, it does not establish why the AKS-managed injection failed.
Microsoft’s AKS release notes for October 25, 2026 explicitly describe protected-system-namespace exclusions for customer mutating admission configurations on AKS Automatic 1.36+. This confirms that the protection is intentional, rather than a CloudNativePG-specific requirement.
- Is this a known issue or a separate injector rollout?
A rollout mismatch is a possibility, not a confirmed diagnosis.
One important distinction: the absence of a matching MutatingWebhookConfiguration does not prove that the AKS injection component is missing. Kubernetes explicitly excludes MutatingWebhookConfiguration and ValidatingWebhookConfiguration objects from ordinary admission-webhook interception. Therefore, enumerating those webhooks cannot establish how AKS implements this mutation. Microsoft separately documents an AKS-managed admissions enforcer. (v1-36.docs.kubernetes.io)
Given the error’s explicit instruction to contact support, open an AKS support request with the minimal reproduction, failure timestamp in UTC, cluster version and region, and the validating policy/binding YAML. Ask Microsoft to verify the managed injection path and its compatibility with the deployed validating policy. Microsoft documents Azure support requests as the escalation path for unresolved AKS issues.
- Will injection duplicate an existing condition?
Kubernetes requires match-condition names to be unique within each webhook. That means appending another condition with the same name is not a valid outcome—but this requirement does not establish whether AKS skips, replaces, or otherwise handles an existing condition. I couldn’t find a documented AKS guarantee for that behavior.
Before removing the workaround, test a copy of the original manifest without the hand-added condition, using an unused configuration name:
kubectl create --dry-run=server -f .\webhook-probe.yaml -o yaml
Server-side dry-run processes admission without persisting the object. Once injection is working, the returned YAML should demonstrate whether the required condition was added. Separately test a manifest that already contains the condition to check coexistence on your cluster. (kubernetes.io)
- Can the protected-namespace list change?
Given the exact-string comparison you observed, your concern is valid: if the policy’s required expression changes and AKS does not first update the submitted value, subsequent matching create/update requests containing the old expression would fail.
Treat the copied expression as a temporary, cluster-specific workaround—not a stable compatibility contract.