<p>What options are available to me if I want to restrict the usage of Priorty Classes, if I'm running a managed Kubernetes service (AKS)?</p>
<p>The use-case here is that, I am as cluster admin want to restrict the usage of these. So that developers are not using those that are supposed to be used by critical components.</p>
<p>Multi-tenant cluster, semi 0-trust policy. This is something that could be &quot;abused&quot;.</p>
<p>Is this something I can achieve with resource quotas even though I'm running Azure Kubernetes Service?
<a href="https://kubernetes.io/docs/concepts/policy/resource-quotas/#limit-priority-class-consumption-by-default" rel="nofollow noreferrer">https://kubernetes.io/docs/concepts/policy/resource-quotas/#limit-priority-class-consumption-by-default</a></p>

<p>Cloud managed cluster does not allow you to customize the api-server. In this case, you can use <a href="https://kubernetes.io/blog/2019/08/06/opa-gatekeeper-policy-and-governance-for-kubernetes/#policies-and-constraints" rel="nofollow noreferrer">opa gatekeeper</a> or <a href="https://kyverno.io/policies/other/allowed_pod_priorities/allowed_pod_priorities/" rel="nofollow noreferrer">kyverno</a> to write rules that reject un-necessary priority class settings.</p>
