Change:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Update . Better documentation on what Kubernetes policies are, the types of policies available, and when should each type be used. Why is this needed Several users tend to confuse policies with network policies or other API objects that provide policy behaviors. With the new ValidatingAdmissionPolicy, there are questions on how that fits with other Kubernetes policy types. There is no doc to cover the types of available policies and clarify where they fit. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Draft PR:
/language en
How about: write text for (page is currently autogenerated) for each page within policy section, identify at the top of the page which kind of policy it is and optionally: in the reference section, add a table of all policy mechanisms in Kubernetes, along with a link to the docs for that mechanism link to that new reference page from
Page for updation: Its a github link where we should add description about the policies, uses and as per the issue is asking for. /sig docs

Discussion:
--- title: "Policies" weight: 90 <ins> no_list: true </ins> description: > <del> Policies you can configure that apply to groups of resources. </del> <ins> Manage security and best-practices with policies. </ins> --- <del> {{< note >}} See [Network Policies](/docs/concepts/services-networking/network-policies/) for documentation about NetworkPolicy in Kubernetes. {{< /note >}} </del> <ins> <!-- overview --> Kubernetes policies are configurations that manage other configurations or runtime behaviors. Kubernetes offers various forms of policies, described below: <!-- body --> ## Apply policies using API objects Some API objects act as policies. Here are some examples: * [NetworkPolicies](/docs/concepts/services-networking/network-policies/) can be used to restrict ingress and egress traffic for a workload. * [LimitRanges](/docs/concepts/policy/limit-range/) manage resource allocation constraints across different object kinds. * [ResourceQuotas](/docs/concepts/policy/resource-quotas/) limit resource consumption for a {{< glossary_tooltip text="namespace" term_id="namespace" >}}. ## Apply policies using admission controllers An {{< glossary_tooltip text="admission controller" term_id="admission-controller" >}} runs in the API server and can validate or mutate API requests. Some admission controllers act to apply policies. For example, the [AlwaysPullImages](/docs/reference/access-authn-authz/admission-controllers/#alwayspullimages) admission controller modifies a new Pod to set the image pull policy to `Always`. Kubernetes has several built-in admission controllers that are configurable via the API server `--enable-admission-plugins` flag. Details on admission controllers, with the complete list of available admission controllers, are documented in a dedicated section: * [Admission Controllers](/docs/reference/access-authn-authz/admission-controllers/) ## Apply policies using ValidatingAdmissionPolicy Validating admission policies allow configurable validation checks to be executed in the API server using the Common Expression Language (CEL). For example, a `ValidatingAdmissionPolicy` can be used to disallow use of the `latest` image tag. A `ValidatingAdmissionPolicy` operates on an API request and can be used to block, audit, and warn users about non-compliant configurations. Details on the `ValidatingAdmissionPolicy` API, with examples, are documented in a dedicated section: * [Validating Admission Policy](/docs/reference/access-authn-authz/validating-admission-policy/) ## Apply policies using dynamic admission control Dynamic admission controllers (or admission webhooks) run outside the API server as separate applications that register to receive webhooks requests to perform validation or mutation of API requests. Dynamic admission controllers can be used to apply policies on API requests and trigger other policy-based workflows. A dynamic admission controller can perform complex checks including those that require retrieval of other cluster resources and external data. For example, an image verification check can lookup data from OCI registries to validate the container image signatures and attestations. Details on dynamic admission control are documented in a dedicated section: * [Dynamic Admission Control](/docs/reference/access-authn-authz/extensible-admission-controllers/) ### Implementations {#implementations-admission-control} {{% thirdparty-content %}} Dynamic Admission Controllers that act as flexible policy engines are being developed in the Kubernetes ecosystem, such as: - [Kubewarden](https://github.com/kubewarden) - [Kyverno](https://kyverno.io) - [OPA Gatekeeper](https://github.com/open-policy-agent/gatekeeper) - [Polaris](https://polaris.docs.fairwinds.com/admission-controller/) ## Apply policies using Kubelet configurations Kubernetes allows configuring the Kubelet on each worker node.  Some Kubelet configurations act as policies: * [Process ID limts and reservations](/docs/concepts/policy/pid-limiting/) are used to limit and reserve allocatable PIDs. * [Node Resource Managers](/docs/concepts/policy/node-resource-managers/) can manage compute, memory, and device resources for latency-critical and high-throughput workloads. </ins>