Policies
Supported Configurations
Running the control plane as a container with:
info
Network policies in the cluster rely on the support for this feature in the control plane cluster. Make sure that your control plane cluster satisfies the network policy prerequisites.
The policies section of vcluster.yaml sets limits and rules for the cluster's workloads.
- Network policy isolates the cluster's traffic from other clusters and the control plane cluster.
- Pod security standard applies a Pod Security Standards level to the cluster's pods.
- Resource quota caps the compute, storage, and object counts the cluster can use.
- Limit range sets default and maximum CPU, memory, and storage per pod or container.
- Central admission control runs admission webhooks on the control plane cluster.
- The admission controller is typically running on the control plane cluster, where the policies enforced by the webhook cannot be changed by the cluster.
- Users could deploy their own admission webhooks to the cluster, but there's little value in doing so, and this configuration is not concerned with that use case.
- Some examples of admission controller projects:
- It's common for organizations to develop an in-house collection of policies that can enforce naming standards and so on.
You can use these settings separately for specific cases, or together, as in the case of Isolated Mode.
Config reference​
For every field under policies, see the policies reference.