Skip to content

Commit b6e3a1f

Browse files
authored
Merge pull request #32680 from my-git9/extend-kubernetes_index
Extend kubernetes index
2 parents 70dbc89 + 99bf6b7 commit b6e3a1f

File tree

1 file changed

+2
-2
lines changed
  • content/zh/docs/concepts/extend-kubernetes

1 file changed

+2
-2
lines changed

content/zh/docs/concepts/extend-kubernetes/_index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -95,10 +95,10 @@ Flags and configuration files may not always be changeable in a hosted Kubernete
9595
有鉴于此,通常应该在没有其他替代方案时才应考虑更改参数标志和配置文件。
9696

9797
<!--
98-
*Built-in Policy APIs*, such as [ResourceQuota](/docs/concepts/policy/resource-quotas/), [PodSecurityPolicies](/docs/concepts/policy/pod-security-policy/), [NetworkPolicy](/docs/concepts/services-networking/network-policies/) and Role-based Access Control ([RBAC](/docs/reference/access-authn-authz/rbac/)), are built-in Kubernetes APIs. APIs are typically used with hosted Kubernetes services and with managed Kubernetes installations. They are declarative and use the same conventions as other Kubernetes resources like pods, so new cluster configuration can be repeatable and be managed the same way as applications. And, where they are stable, they enjoy a [defined support policy](/docs/reference/using-api/deprecation-policy/) like other Kubernetes APIs. For these reasons, they are preferred over *configuration files* and *flags* where suitable.
98+
*Built-in Policy APIs*, such as [ResourceQuota](/docs/concepts/policy/resource-quotas/), [PodSecurityPolicies](/docs/concepts/security/pod-security-policy/), [NetworkPolicy](/docs/concepts/services-networking/network-policies/) and Role-based Access Control ([RBAC](/docs/reference/access-authn-authz/rbac/)), are built-in Kubernetes APIs. APIs are typically used with hosted Kubernetes services and with managed Kubernetes installations. They are declarative and use the same conventions as other Kubernetes resources like pods, so new cluster configuration can be repeatable and be managed the same way as applications. And, where they are stable, they enjoy a [defined support policy](/docs/reference/using-api/deprecation-policy/) like other Kubernetes APIs. For these reasons, they are preferred over *configuration files* and *flags* where suitable.
9999
-->
100100
*内置的策略 API*,例如[ResourceQuota](/zh/docs/concepts/policy/resource-quotas/)
101-
[PodSecurityPolicies](/zh/docs/concepts/policy/pod-security-policy/)
101+
[PodSecurityPolicies](/zh/docs/concepts/security/pod-security-policy/)
102102
[NetworkPolicy](/zh/docs/concepts/services-networking/network-policies/)
103103
和基于角色的访问控制([RBAC](/zh/docs/reference/access-authn-authz/rbac/)
104104
等等都是内置的 Kubernetes API。

0 commit comments

Comments
 (0)