blocks|key|1684861|text|我们可以在Kubernetes文档中读到关于Pod+Security+Policies的内容。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1684862|1684863|实例安全策略是一个群集级别的资源，用于控制实例规范的安全敏感方面。PodSecurityPolicy对象定义了pod运行时必须满足的一组条件，才能被系统接受，以及相关字段的默认值。|blockquote|style|CODE|1684864|1684865|1684866|您应该使用RBAC并设置将使用所需PSP的Role。|1684867|1684868|如果使用RoleBinding+(而不是ClusterRoleBinding)，它将仅授予在与绑定相同的名称空间中运行的pods的使用权限。这可以与系统组配对，以授予对名称空间中运行的所有pod的访问权限：|1684869|1684870|1684871|#+Authorize+all+service+accounts+in+a+namespace:
-+kind:+Group
++apiGroup:+rbac.authorization.k8s.io
++name:+system:serviceaccounts
#+Or+equivalently,+all+authenticated+users+in+a+namespace:
-+kind:+Group
++apiGroup:+rbac.authorization.k8s.io
++name:+system:authenticated|code-block|syntax|javascript|1684872|你还应该看看Using+PodSecurityPolicies和Kubernetes:+Assigning+Pod+Security+Policies+with+RBAC。|1684873|希望这能有所帮助。|1684874|entityMap|0|LINK|mutability|MUTABLE|url|https://kubernetes.io/docs/concepts/policy/pod-security-policy/|1|https://kubernetes.io/docs/reference/access-authn-authz/rbac/|2|https://cloud.google.com/kubernetes-engine/docs/how-to/pod-security-policies|3|https://medium.com/coryodaniel/kubernetes-assigning-pod-security-policies-with-rbac-2ad2e847c754^0|M|L|0|0|0|X|H|0|0|0|H|3|L|4|5|4|1|0|0|4|B|K|I|0|0|0|0|6|P|2|W|1H|3|0|0^^$0|@$1|2|3|4|5|6|7|1F|8|@]|9|@$A|1G|B|1H|1|1I]]|C|$]]|$1|D|3|-4|5|6|7|1J|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|1K|8|@$A|1L|B|1M|H|I]]|9|@]|C|$]]|$1|J|3|-4|5|6|7|1N|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|1O|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|1P|8|@$A|1Q|B|1R|H|I]|$A|1S|B|1T|H|I]]|9|@$A|1U|B|1V|1|1W]]|C|$]]|$1|N|3|-4|5|6|7|1X|8|@]|9|@]|C|$]]|$1|O|3|P|5|G|7|1Y|8|@$A|1Z|B|20|H|I]|$A|21|B|22|H|I]]|9|@]|C|$]]|$1|Q|3|-4|5|6|7|23|8|@]|9|@]|C|$]]|$1|R|3|-4|5|6|7|24|8|@]|9|@]|C|$]]|$1|S|3|T|5|U|7|25|8|@]|9|@]|C|$V|W]]|$1|X|3|Y|5|6|7|26|8|@]|9|@$A|27|B|28|1|29]|$A|2A|B|2B|1|2C]]|C|$]]|$1|Z|3|10|5|6|7|2D|8|@]|9|@]|C|$]]|$1|11|3|-4|5|6|7|2E|8|@]|9|@]|C|$]]]|12|$13|$5|14|15|16|C|$17|18]]|19|$5|14|15|16|C|$17|1A]]|1B|$5|14|15|16|C|$17|1C]]|1D|$5|14|15|16|C|$17|1E]]]]

As we can read in the Kubernetes documentation about <a href="https://kubernetes.io/docs/concepts/policy/pod-security-policy/" rel="nofollow noreferrer">Pod Security Policies</a>.

<blockquote>
 A Pod Security Policy is a cluster-level resource that controls security sensitive aspects of the pod specification. The <code>PodSecurityPolicy</code> objects define a set of conditions that a pod must run with in order to be accepted into the system, as well as defaults for the related fields.
</blockquote>

You should use <a href="https://kubernetes.io/docs/reference/access-authn-authz/rbac/" rel="nofollow noreferrer">RBAC</a> and setup <code>Role</code> which will use desired <code>PSP</code>.

<blockquote>
 If a <code>RoleBinding</code> (not a <code>ClusterRoleBinding</code>) is used, it will only grant usage for pods being run in the same namespace as the binding. This can be paired with system groups to grant access to all pods run in the namespace:
</blockquote>

<pre><code># Authorize all service accounts in a namespace:
- kind: Group
 apiGroup: rbac.authorization.k8s.io
 name: system:serviceaccounts
# Or equivalently, all authenticated users in a namespace:
- kind: Group
 apiGroup: rbac.authorization.k8s.io
 name: system:authenticated
</code></pre>

You should also check out <a href="https://cloud.google.com/kubernetes-engine/docs/how-to/pod-security-policies" rel="nofollow noreferrer">Using PodSecurityPolicies</a> and <a href="https://medium.com/coryodaniel/kubernetes-assigning-pod-security-policies-with-rbac-2ad2e847c754" rel="nofollow noreferrer">Kubernetes: Assigning Pod Security Policies with RBAC</a>.

Hope this helps.

blocks|key|3379468|text|Pod+security+policies是一个集群级别的资源，所以在普通Kubernetes中没有当前的方法来做你需要的事情。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3379469|但是，Rancher向集群添加了Projects的概念，您可以将Pod+Security策略应用于项目。|3379470|注意-他们仍然建议在群集级别使用Pod安全策略。|3379471|或者，@Crou的答案也是通过基于角色的访问控制和RoleBindings实现它的一个很好的选择|3379472|entityMap|0|LINK|mutability|MUTABLE|url|https://kubernetes.io/docs/concepts/policy/pod-security-policy/|1|https://rancher.com/docs/rancher/v2.x/en/cluster-admin/projects-and-namespaces/^0|0|L|0|0|G|8|1|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|F|3|G|5|6|7|11|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]|R|$5|M|N|O|C|$P|S]]]]

<a href="https://kubernetes.io/docs/concepts/policy/pod-security-policy/" rel="nofollow noreferrer">Pod security policies</a> are a cluster level resource so there is no current way to do what you need in vanilla Kubernetes. 

However Rancher adds a concept of <a href="https://rancher.com/docs/rancher/v2.x/en/cluster-admin/projects-and-namespaces/" rel="nofollow noreferrer">Projects</a> to the cluster and you can apply Pod Security policies to Projects. 

NOTE - They still recommend using Pod Security Polices at a cluster level. 

Alternatively @Crou's answer is also a good choice to implement it via RBAC and RoleBindings

How can I apply a PSP (PodSecurityPolicy) only for the <code>kube-system</code> namespace and another PSP for all other namespaces?

Can a Pod Security Policy be applied to a namespace?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

如何仅对kube-system名称空间应用PSP (PodSecurityPolicy)，并将另一个PSP应用于所有其他名称空间？

问Pod安全策略是否可以应用于命名空间？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Pod安全策略是否可以应用于命名空间？EN