2017-09-03 15:58:39 +08:00
<!DOCTYPE HTML>
< html lang = "zh-cn" >
< head >
< meta charset = "UTF-8" >
< meta content = "text/html; charset=utf-8" http-equiv = "Content-Type" >
< title > 2.2.1.3 Pod安全策略 · Kubernetes Handbook< / title >
< meta http-equiv = "X-UA-Compatible" content = "IE=edge" / >
< meta name = "description" content = "" >
< meta name = "generator" content = "GitBook 3.2.2" >
< meta name = "author" content = "Jimmy Song" >
< link rel = "stylesheet" href = "../gitbook/style.css" >
< link rel = "stylesheet" href = "../gitbook/gitbook-plugin-splitter/splitter.css" >
< link rel = "stylesheet" href = "../gitbook/gitbook-plugin-page-toc-button/plugin.css" >
< link rel = "stylesheet" href = "../gitbook/gitbook-plugin-image-captions/image-captions.css" >
< link rel = "stylesheet" href = "../gitbook/gitbook-plugin-page-footer-ex/style/plugin.css" >
< link rel = "stylesheet" href = "../gitbook/gitbook-plugin-search-plus/search.css" >
< link rel = "stylesheet" href = "../gitbook/gitbook-plugin-highlight/website.css" >
< link rel = "stylesheet" href = "../gitbook/gitbook-plugin-fontsettings/website.css" >
< meta name = "HandheldFriendly" content = "true" / >
< meta name = "viewport" content = "width=device-width, initial-scale=1, user-scalable=no" >
< meta name = "apple-mobile-web-app-capable" content = "yes" >
< meta name = "apple-mobile-web-app-status-bar-style" content = "black" >
< link rel = "apple-touch-icon-precomposed" sizes = "152x152" href = "../gitbook/images/apple-touch-icon-precomposed-152.png" >
< link rel = "shortcut icon" href = "../gitbook/images/favicon.ico" type = "image/x-icon" >
< link rel = "next" href = "node.html" / >
< link rel = "prev" href = "init-containers.html" / >
< / head >
< body >
< div class = "book" >
< div class = "book-summary" >
< div id = "book-search-input" role = "search" >
< input type = "text" placeholder = "輸入並搜尋" / >
< / div >
< nav role = "navigation" >
< ul class = "summary" >
< li class = "chapter " data-level = "1.1" data-path = "../" >
< a href = "../" >
1. 前言
< / a >
< / li >
< li class = "chapter " data-level = "1.2" data-path = "./" >
< a href = "./" >
2. 概念原理
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.2.1" data-path = "concepts.html" >
< a href = "concepts.html" >
2.1 设计理念
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2" data-path = "objects.html" >
< a href = "objects.html" >
2.2 Objects
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.2.2.1" data-path = "pod-overview.html" >
< a href = "pod-overview.html" >
2.2.1 Pod
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.2.2.1.1" data-path = "pod.html" >
< a href = "pod.html" >
2.2.1.1 Pod解析
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.1.2" data-path = "init-containers.html" >
< a href = "init-containers.html" >
2.2.1.2 Init容器
< / a >
< / li >
< li class = "chapter active" data-level = "1.2.2.1.3" data-path = "pod-security-policy.html" >
< a href = "pod-security-policy.html" >
2.2.1.3 Pod安全策略
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.2.2.2" data-path = "node.html" >
< a href = "node.html" >
2.2.2 Node
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.3" data-path = "namespace.html" >
< a href = "namespace.html" >
2.2.3 Namespace
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.4" data-path = "service.html" >
< a href = "service.html" >
2.2.4 Service
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.5" data-path = "volume.html" >
< a href = "volume.html" >
2.2.5 Volume和Persistent Volume
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.6" data-path = "deployment.html" >
< a href = "deployment.html" >
2.2.6 Deployment
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.7" data-path = "secret.html" >
< a href = "secret.html" >
2.2.7 Secret
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.8" data-path = "statefulset.html" >
< a href = "statefulset.html" >
2.2.8 StatefulSet
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.9" data-path = "daemonset.html" >
< a href = "daemonset.html" >
2.2.9 DaemonSet
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.10" data-path = "serviceaccount.html" >
< a href = "serviceaccount.html" >
2.2.10 ServiceAccount
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.11" data-path = "replicaset.html" >
< a href = "replicaset.html" >
2.2.11 ReplicationController和ReplicaSet
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.12" data-path = "job.html" >
< a href = "job.html" >
2.2.12 Job
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.13" data-path = "cronjob.html" >
< a href = "cronjob.html" >
2.2.13 CronJob
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.14" data-path = "ingress.html" >
< a href = "ingress.html" >
2.2.14 Ingress
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.15" data-path = "configmap.html" >
< a href = "configmap.html" >
2.2.15 ConfigMap
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.16" data-path = "horizontal-pod-autoscaling.html" >
< a href = "horizontal-pod-autoscaling.html" >
2.2.16 Horizontal Pod Autoscaling
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.17" data-path = "label.html" >
< a href = "label.html" >
2.2.17 Label
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.18" data-path = "garbage-collection.html" >
< a href = "garbage-collection.html" >
2.2.18 垃圾收集
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.19" data-path = "network-policy.html" >
< a href = "network-policy.html" >
2.2.19 NetworkPolicy
< / a >
< / li >
< / ul >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.3" data-path = "../guide/" >
< a href = "../guide/" >
3. 用户指南
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.3.1" data-path = "../guide/resource-configuration.html" >
< a href = "../guide/resource-configuration.html" >
3.1 资源配置
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.3.1.1" data-path = "../guide/configure-liveness-readiness-probes.html" >
< a href = "../guide/configure-liveness-readiness-probes.html" >
3.1.1 配置Pod的liveness和readiness探针
< / a >
< / li >
< li class = "chapter " data-level = "1.3.1.2" data-path = "../guide/configure-pod-service-account.html" >
< a href = "../guide/configure-pod-service-account.html" >
3.1.2 配置Pod的Service Account
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.3.2" data-path = "../guide/command-usage.html" >
< a href = "../guide/command-usage.html" >
3.2 命令使用
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.3.2.1" data-path = "../guide/using-kubectl.html" >
< a href = "../guide/using-kubectl.html" >
3.2.1 使用kubectl
< / a >
< / li >
< / ul >
< / li >
2017-09-07 12:29:13 +08:00
< li class = "chapter " data-level = "1.3.3" data-path = "../guide/cluster-security-management.html" >
2017-09-03 15:58:39 +08:00
2017-09-07 12:29:13 +08:00
< a href = "../guide/cluster-security-management.html" >
2017-09-03 15:58:39 +08:00
2017-09-07 12:29:13 +08:00
3.3 集群安全性管理
2017-09-03 15:58:39 +08:00
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.3.3.1" data-path = "../guide/managing-tls-in-a-cluster.html" >
< a href = "../guide/managing-tls-in-a-cluster.html" >
3.3.1 管理集群中的TLS
< / a >
< / li >
< li class = "chapter " data-level = "1.3.3.2" data-path = "../guide/kubelet-authentication-authorization.html" >
< a href = "../guide/kubelet-authentication-authorization.html" >
3.3.2 kubelet的认证授权
< / a >
< / li >
< li class = "chapter " data-level = "1.3.3.3" data-path = "../guide/tls-bootstrapping.html" >
< a href = "../guide/tls-bootstrapping.html" >
3.3.3 TLS bootstrap
< / a >
< / li >
< li class = "chapter " data-level = "1.3.3.4" data-path = "../guide/kubectl-user-authentication-authorization.html" >
< a href = "../guide/kubectl-user-authentication-authorization.html" >
3.3.4 kubectl的用户认证授权
< / a >
< / li >
< li class = "chapter " data-level = "1.3.3.5" data-path = "../guide/rbac.html" >
< a href = "../guide/rbac.html" >
3.3.5 RBAC——基于角色的访问控制
< / a >
2017-09-07 14:13:59 +08:00
< / li >
< li class = "chapter " data-level = "1.3.3.6" data-path = "../guide/ip-masq-agent.html" >
< a href = "../guide/ip-masq-agent.html" >
3.3.6 IP伪装代理
< / a >
2017-09-03 15:58:39 +08:00
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.3.4" data-path = "../guide/access-kubernetes-cluster.html" >
< a href = "../guide/access-kubernetes-cluster.html" >
3.4 访问 Kubernetes 集群
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.3.4.1" data-path = "../guide/access-cluster.html" >
< a href = "../guide/access-cluster.html" >
3.4.1 访问集群
< / a >
< / li >
< li class = "chapter " data-level = "1.3.4.2" data-path = "../guide/authenticate-across-clusters-kubeconfig.html" >
< a href = "../guide/authenticate-across-clusters-kubeconfig.html" >
3.4.2 使用 kubeconfig 文件配置跨集群认证
< / a >
< / li >
< li class = "chapter " data-level = "1.3.4.3" data-path = "../guide/connecting-to-applications-port-forward.html" >
< a href = "../guide/connecting-to-applications-port-forward.html" >
3.4.3 通过端口转发访问集群中的应用程序
< / a >
< / li >
< li class = "chapter " data-level = "1.3.4.4" data-path = "../guide/service-access-application-cluster.html" >
< a href = "../guide/service-access-application-cluster.html" >
3.4.4 使用 service 访问群集中的应用程序
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.3.5" data-path = "../guide/application-development-deployment-flow.html" >
< a href = "../guide/application-development-deployment-flow.html" >
3.5 在kubernetes中开发部署应用
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.3.5.1" data-path = "../guide/deploy-applications-in-kubernetes.html" >
< a href = "../guide/deploy-applications-in-kubernetes.html" >
3.5.1 适用于kubernetes的应用开发部署流程
< / a >
< / li >
< li class = "chapter " data-level = "1.3.5.2" data-path = "../guide/migrating-hadoop-yarn-to-kubernetes.html" >
< a href = "../guide/migrating-hadoop-yarn-to-kubernetes.html" >
3.5.2 迁移传统应用到kubernetes中——以Hadoop YARN为例
< / a >
< / li >
< / ul >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.4" data-path = "../practice/" >
< a href = "../practice/" >
4. 最佳实践
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.4.1" data-path = "../practice/install-kbernetes1.6-on-centos.html" >
< a href = "../practice/install-kbernetes1.6-on-centos.html" >
4.1 在CentOS上部署kubernetes1.6集群
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.4.1.1" data-path = "../practice/create-tls-and-secret-key.html" >
< a href = "../practice/create-tls-and-secret-key.html" >
4.1.1 创建TLS证书和秘钥
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.2" data-path = "../practice/create-kubeconfig.html" >
< a href = "../practice/create-kubeconfig.html" >
4.1.2 创建kubeconfig文件
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.3" data-path = "../practice/etcd-cluster-installation.html" >
< a href = "../practice/etcd-cluster-installation.html" >
4.1.3 创建高可用etcd集群
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.4" data-path = "../practice/kubectl-installation.html" >
< a href = "../practice/kubectl-installation.html" >
4.1.4 安装kubectl命令行工具
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.5" data-path = "../practice/master-installation.html" >
< a href = "../practice/master-installation.html" >
4.1.5 部署master节点
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.6" data-path = "../practice/node-installation.html" >
< a href = "../practice/node-installation.html" >
4.1.6 部署node节点
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.7" data-path = "../practice/kubedns-addon-installation.html" >
< a href = "../practice/kubedns-addon-installation.html" >
4.1.7 安装kubedns插件
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.8" data-path = "../practice/dashboard-addon-installation.html" >
< a href = "../practice/dashboard-addon-installation.html" >
4.1.8 安装dashboard插件
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.9" data-path = "../practice/heapster-addon-installation.html" >
< a href = "../practice/heapster-addon-installation.html" >
4.1.9 安装heapster插件
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.10" data-path = "../practice/efk-addon-installation.html" >
< a href = "../practice/efk-addon-installation.html" >
4.1.10 安装EFK插件
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.4.2" data-path = "../practice/service-discovery-and-loadbalancing.html" >
< a href = "../practice/service-discovery-and-loadbalancing.html" >
4.2 服务发现与负载均衡
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.4.2.1" data-path = "../practice/traefik-ingress-installation.html" >
< a href = "../practice/traefik-ingress-installation.html" >
4.2.1 安装Traefik ingress
< / a >
< / li >
< li class = "chapter " data-level = "1.4.2.2" data-path = "../practice/distributed-load-test.html" >
< a href = "../practice/distributed-load-test.html" >
4.2.2 分布式负载测试
< / a >
< / li >
< li class = "chapter " data-level = "1.4.2.3" data-path = "../practice/network-and-cluster-perfermance-test.html" >
< a href = "../practice/network-and-cluster-perfermance-test.html" >
4.2.3 网络和集群性能测试
< / a >
< / li >
< li class = "chapter " data-level = "1.4.2.4" data-path = "../practice/edge-node-configuration.html" >
< a href = "../practice/edge-node-configuration.html" >
4.2.4 边缘节点配置
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.4.3" data-path = "../practice/operation.html" >
< a href = "../practice/operation.html" >
4.3 运维管理
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.4.3.1" data-path = "../practice/service-rolling-update.html" >
< a href = "../practice/service-rolling-update.html" >
4.3.1 服务滚动升级
< / a >
< / li >
< li class = "chapter " data-level = "1.4.3.2" data-path = "../practice/app-log-collection.html" >
< a href = "../practice/app-log-collection.html" >
4.3.2 应用日志收集
< / a >
< / li >
< li class = "chapter " data-level = "1.4.3.3" data-path = "../practice/configuration-best-practice.html" >
< a href = "../practice/configuration-best-practice.html" >
4.3.3 配置最佳实践
< / a >
< / li >
< li class = "chapter " data-level = "1.4.3.4" data-path = "../practice/monitor.html" >
< a href = "../practice/monitor.html" >
4.3.4 集群及应用监控
< / a >
< / li >
< li class = "chapter " data-level = "1.4.3.5" data-path = "../practice/jenkins-ci-cd.html" >
< a href = "../practice/jenkins-ci-cd.html" >
4.3.5 使用Jenkins进行持续构建与发布
< / a >
< / li >
< li class = "chapter " data-level = "1.4.3.6" data-path = "../practice/data-persistence-problem.html" >
< a href = "../practice/data-persistence-problem.html" >
4.3.6 数据持久化问题
< / a >
< / li >
< li class = "chapter " data-level = "1.4.3.7" data-path = "../practice/manage-compute-resources-container.html" >
< a href = "../practice/manage-compute-resources-container.html" >
4.3.7 管理容器的计算资源
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.4.4" data-path = "../practice/storage.html" >
< a href = "../practice/storage.html" >
4.4 存储管理
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.4.4.1" data-path = "../practice/glusterfs.html" >
< a href = "../practice/glusterfs.html" >
4.4.1 GlusterFS
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.4.4.1.1" data-path = "../practice/using-glusterfs-for-persistent-storage.html" >
< a href = "../practice/using-glusterfs-for-persistent-storage.html" >
4.4.1.1 使用GlusterFS做持久化存储
< / a >
< / li >
< li class = "chapter " data-level = "1.4.4.1.2" data-path = "../practice/storage-for-containers-using-glusterfs-with-openshift.html" >
< a href = "../practice/storage-for-containers-using-glusterfs-with-openshift.html" >
4.4.1.2 在OpenShift中使用GlusterFS做持久化存储
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.4.4.2" data-path = "../practice/cephfs.html" >
< a href = "../practice/cephfs.html" >
4.4.2 CephFS
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.4.4.2.1" data-path = "../practice/using-ceph-for-persistent-storage.html" >
< a href = "../practice/using-ceph-for-persistent-storage.html" >
4.4.2.1 使用Ceph做持久化存储
< / a >
< / li >
< / ul >
< / li >
< / ul >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.5" data-path = "../usecases/" >
< a href = "../usecases/" >
5. 领域应用
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.5.1" data-path = "../usecases/microservices.html" >
< a href = "../usecases/microservices.html" >
5.1 微服务架构
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.5.1.1" data-path = "../usecases/istio.html" >
< a href = "../usecases/istio.html" >
5.1.1 Istio
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.5.1.1.1" data-path = "../usecases/istio-installation.html" >
< a href = "../usecases/istio-installation.html" >
5.1.1.1 安装istio
< / a >
< / li >
< li class = "chapter " data-level = "1.5.1.1.2" data-path = "../usecases/configuring-request-routing.html" >
< a href = "../usecases/configuring-request-routing.html" >
5.1.1.2 配置请求的路由规则
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.5.1.2" data-path = "../usecases/linkerd.html" >
< a href = "../usecases/linkerd.html" >
5.1.2 Linkerd
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.5.1.2.1" data-path = "../usecases/linkerd-user-guide.html" >
< a href = "../usecases/linkerd-user-guide.html" >
5.1.2.1 Linkerd 使用指南
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.5.1.3" data-path = "../usecases/service-discovery-in-microservices.html" >
< a href = "../usecases/service-discovery-in-microservices.html" >
5.1.3 微服务中的服务发现
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.5.2" data-path = "../usecases/big-data.html" >
< a href = "../usecases/big-data.html" >
5.2 大数据
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.5.2.1" data-path = "../usecases/spark-standalone-on-kubernetes.html" >
< a href = "../usecases/spark-standalone-on-kubernetes.html" >
5.2.1 Spark standalone on Kubernetes
< / a >
< / li >
2017-09-14 15:57:50 +08:00
< li class = "chapter " data-level = "1.5.2.2" data-path = "../usecases/running-spark-with-kubernetes-native-scheduler.html" >
2017-09-03 15:58:39 +08:00
2017-09-14 15:57:50 +08:00
< a href = "../usecases/running-spark-with-kubernetes-native-scheduler.html" >
2017-09-03 15:58:39 +08:00
5.2.2 运行支持kubernetes原生调度的Spark程序
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.5.3" data-path = "../usecases/serverless.html" >
< a href = "../usecases/serverless.html" >
5.3 Serverless架构
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.6" data-path = "../develop/" >
< a href = "../develop/" >
6. 开发指南
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.6.1" data-path = "../develop/developing-environment.html" >
< a href = "../develop/developing-environment.html" >
6.1 开发环境搭建
< / a >
< / li >
< li class = "chapter " data-level = "1.6.2" data-path = "../develop/testing.html" >
< a href = "../develop/testing.html" >
6.2 单元测试和集成测试
< / a >
< / li >
< li class = "chapter " data-level = "1.6.3" data-path = "../develop/client-go-sample.html" >
< a href = "../develop/client-go-sample.html" >
6.3 client-go示例
< / a >
< / li >
< li class = "chapter " data-level = "1.6.4" data-path = "../develop/contribute.html" >
< a href = "../develop/contribute.html" >
6.4 社区贡献
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.7" data-path = "../appendix/" >
< a href = "../appendix/" >
7. 附录
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.7.1" data-path = "../appendix/docker-best-practice.html" >
< a href = "../appendix/docker-best-practice.html" >
7.1 Docker最佳实践
< / a >
< / li >
< li class = "chapter " data-level = "1.7.2" data-path = "../appendix/issues.html" >
< a href = "../appendix/issues.html" >
7.2 问题记录
< / a >
< / li >
< li class = "chapter " data-level = "1.7.3" data-path = "../appendix/tricks.html" >
< a href = "../appendix/tricks.html" >
7.3 使用技巧
< / a >
< / li >
< / ul >
< / li >
< li class = "divider" > < / li >
< li >
< a href = "https://www.gitbook.com" target = "blank" class = "gitbook-link" >
本書使用 GitBook 釋出
< / a >
< / li >
< / ul >
< / nav >
< / div >
< div class = "book-body" >
< div class = "body-inner" >
< div class = "book-header" role = "navigation" >
<!-- Title -->
< h1 >
< i class = "fa fa-circle-o-notch fa-spin" > < / i >
< a href = ".." > 2.2.1.3 Pod安全策略< / a >
< / h1 >
< / div >
< div class = "page-wrapper" tabindex = "-1" role = "main" >
< div class = "page-inner" >
< div class = "search-plus" id = "book-search-results" >
< div class = "search-noresults" >
< section class = "normal markdown-section" >
< h1 id = "pod-安全策略" > Pod 安 全 策 略 < / h1 >
< p > < code > PodSecurityPolicy< / code > 类 型 的 对 象 能 够 控 制 ， 是 否 可 以 向 Pod 发 送 请 求 ， 该 Pod 能 够 影 响 被 应 用 到 Pod 和 容 器 的 < code > SecurityContext< / code > 。 查 看 < a href = "https://git.k8s.io/community/contributors/design-proposals/security-context-constraints.md" target = "_blank" > Pod 安 全 策 略 建 议 < / a > 获 取 更 多 信 息 。 < / p >
< h2 id = "什么是-pod-安全策略？" > 什 么 是 Pod 安 全 策 略 ？ < / h2 >
< p > < em > Pod 安 全 策 略 < / em > 是 集 群 级 别 的 资 源 ， 它 能 够 控 制 Pod 运 行 的 行 为 ， 以 及 它 具 有 访 问 什 么 的 能 力 。 < code > PodSecurityPolicy< / code > 对 象 定 义 了 一 组 条 件 ， 指 示 Pod 必 须 按 系 统 所 能 接 受 的 顺 序 运 行 。 它 们 允 许 管 理 员 控 制 如 下 方 面 ： < / p >
< table >
< thead >
< tr >
< th > 控 制 面 < / th >
< th > 字 段 名 称 < / th >
< / tr >
< / thead >
< tbody >
< tr >
< td > 已 授 权 容 器 的 运 行 < / td >
< td > < code > privileged< / code > < / td >
< / tr >
< tr >
< td > 为 容 器 添 加 默 认 的 一 组 能 力 < / td >
< td > < code > defaultAddCapabilities< / code > < / td >
< / tr >
< tr >
< td > 为 容 器 去 掉 某 些 能 力 < / td >
< td > < code > requiredDropCapabilities< / code > < / td >
< / tr >
< tr >
< td > 容 器 能 够 请 求 添 加 某 些 能 力 < / td >
< td > < code > allowedCapabilities< / code > < / td >
< / tr >
< tr >
< td > 控 制 卷 类 型 的 使 用 < / td >
< td > < a href = "https://kubernetes.io/docs/concepts/policy/pod-security-policy/#controlling-volumes" target = "_blank" > < code > volumes< / code > < / a > < / td >
< / tr >
< tr >
< td > 主 机 网 络 的 使 用 < / td >
< td > < a href = "https://kubernetes.io/docs/concepts/policy/pod-security-policy/#host-network" target = "_blank" > < code > hostNetwork< / code > < / a > < / td >
< / tr >
< tr >
< td > 主 机 端 口 的 使 用 < / td >
< td > < code > hostPorts< / code > < / td >
< / tr >
< tr >
< td > 主 机 PID namespace 的 使 用 < / td >
< td > < code > hostPID< / code > < / td >
< / tr >
< tr >
< td > 主 机 IPC namespace 的 使 用 < / td >
< td > < code > hostIPC< / code > < / td >
< / tr >
< tr >
< td > 主 机 路 径 的 使 用 < / td >
< td > < a href = "https://kubernetes.io/docs/concepts/policy/pod-security-policy/#allowed-host-paths" target = "_blank" > < code > allowedHostPaths< / code > < / a > < / td >
< / tr >
< tr >
< td > 容 器 的 SELinux 上 下 文 < / td >
< td > < a href = "https://kubernetes.io/docs/concepts/policy/pod-security-policy/#selinux" target = "_blank" > < code > seLinux< / code > < / a > < / td >
< / tr >
< tr >
< td > 用 户 ID< / td >
< td > < a href = "https://kubernetes.io/docs/concepts/policy/pod-security-policy/#runasuser" target = "_blank" > < code > runAsUser< / code > < / a > < / td >
< / tr >
< tr >
< td > 配 置 允 许 的 补 充 组 < / td >
< td > < a href = "https://kubernetes.io/docs/concepts/policy/pod-security-policy/#supplementalgroups" target = "_blank" > < code > supplementalGroups< / code > < / a > < / td >
< / tr >
< tr >
< td > 分 配 拥 有 Pod 数 据 卷 的 FSGroup< / td >
< td > < a href = "https://kubernetes.io/docs/concepts/policy/pod-security-policy/#fsgroup" target = "_blank" > < code > fsGroup< / code > < / a > < / td >
< / tr >
< tr >
< td > 必 须 使 用 一 个 只 读 的 root 文 件 系 统 < / td >
< td > < code > readOnlyRootFilesystem< / code > < / td >
< / tr >
< / tbody >
< / table >
< p > < em > Pod 安 全 策 略 < / em > 由 设 置 和 策 略 组 成 ， 它 们 能 够 控 制 Pod 访 问 的 安 全 特 征 。 这 些 设 置 分 为 如 下 三 类 ： < / p >
< ul >
< li > < em > 基 于 布 尔 值 控 制 < / em > ： 这 种 类 型 的 字 段 默 认 为 最 严 格 限 制 的 值 。 < / li >
< li > < em > 基 于 被 允 许 的 值 集 合 控 制 < / em > ： 这 种 类 型 的 字 段 会 与 这 组 值 进 行 对 比 ， 以 确 认 值 被 允 许 。 < / li >
< li > < em > 基 于 策 略 控 制 < / em > ： 设 置 项 通 过 一 种 策 略 提 供 的 机 制 来 生 成 该 值 ， 这 种 机 制 能 够 确 保 指 定 的 值 落 在 被 允 许 的 这 组 值 中 。 < / li >
< / ul >
< h3 id = "runasuser" > RunAsUser< / h3 >
< ul >
< li > < em > MustRunAs< / em > - 必 须 配 置 一 个 < code > range< / code > 。 使 用 该 范 围 内 的 第 一 个 值 作 为 默 认 值 。 验 证 是 否 不 在 配 置 的 该 范 围 内 。 < / li >
< li > < em > MustRunAsNonRoot< / em > - 要 求 提 交 的 Pod 具 有 非 零 < code > runAsUser< / code > 值 ， 或 在 镜 像 中 定 义 了 < code > USER< / code > 环 境 变 量 。 不 提 供 默 认 值 。 < / li >
< li > < em > RunAsAny< / em > - 没 有 提 供 默 认 值 。 允 许 指 定 任 何 < code > runAsUser< / code > 。 < / li >
< / ul >
< h3 id = "selinux" > SELinux< / h3 >
< ul >
< li > < em > MustRunAs< / em > - 如 果 没 有 使 用 预 分 配 的 值 ， 必 须 配 置 < code > seLinuxOptions< / code > 。 默 认 使 用 < code > seLinuxOptions< / code > 。 验 证 < code > seLinuxOptions< / code > 。 < / li >
< li > < em > RunAsAny< / em > - 没 有 提 供 默 认 值 。 允 许 任 意 指 定 的 < code > seLinuxOptions< / code > ID。 < / li >
< / ul >
< h3 id = "supplementalgroups" > SupplementalGroups< / h3 >
< ul >
< li > < em > MustRunAs< / em > - 至 少 需 要 指 定 一 个 范 围 。 默 认 使 用 第 一 个 范 围 的 最 小 值 。 验 证 所 有 范 围 的 值 。 < / li >
< li > < em > RunAsAny< / em > - 没 有 提 供 默 认 值 。 允 许 任 意 指 定 的 < code > supplementalGroups< / code > ID。 < / li >
< / ul >
< h3 id = "fsgroup" > FSGroup< / h3 >
< ul >
< li > < em > MustRunAs< / em > - 至 少 需 要 指 定 一 个 范 围 。 默 认 使 用 第 一 个 范 围 的 最 小 值 。 验 证 在 第 一 个 范 围 内 的 第 一 个 ID。 < / li >
< li > < em > RunAsAny< / em > - 没 有 提 供 默 认 值 。 允 许 任 意 指 定 的 < code > fsGroup< / code > ID。 < / li >
< / ul >
< h3 id = "控制卷" > 控 制 卷 < / h3 >
< p > 通 过 设 置 PSP 卷 字 段 ， 能 够 控 制 具 体 卷 类 型 的 使 用 。 当 创 建 一 个 卷 的 时 候 ， 与 该 字 段 相 关 的 已 定 义 卷 可 以 允 许 设 置 如 下 值 ： < / p >
< ol >
< li > azureFile< / li >
< li > azureDisk< / li >
< li > flocker< / li >
< li > flexVolume< / li >
< li > hostPath< / li >
< li > emptyDir< / li >
< li > gcePersistentDisk< / li >
< li > awsElasticBlockStore< / li >
< li > gitRepo< / li >
< li > secret< / li >
< li > nfs< / li >
< li > iscsi< / li >
< li > glusterfs< / li >
< li > persistentVolumeClaim< / li >
< li > rbd< / li >
< li > cinder< / li >
< li > cephFS< / li >
< li > downwardAPI< / li >
< li > fc< / li >
< li > configMap< / li >
< li > vsphereVolume< / li >
< li > quobyte< / li >
< li > photonPersistentDisk< / li >
< li > projected< / li >
< li > portworxVolume< / li >
< li > scaleIO< / li >
< li > storageos< / li >
< li > * (allow all volumes)< / li >
< / ol >
< p > 对 新 的 PSP， 推 荐 允 许 的 卷 的 最 小 集 合 包 括 ： configMap、 downwardAPI、 emptyDir、 persistentVolumeClaim、 secret 和 projected。 < / p >
< h3 id = "主机网络" > 主 机 网 络 < / h3 >
< ul >
< li > < em > HostPorts< / em > ， 默 认 为 < code > empty< / code > 。 < code > HostPortRange< / code > 列 表 通 过 < code > min< / code > (包 含 ) and < code > max< / code > (包 含 ) 来 定 义 ， 指 定 了 被 允 许 的 主 机 端 口 。 < / li >
< / ul >
< h3 id = "允许的主机路径" > 允 许 的 主 机 路 径 < / h3 >
< ul >
< li > < em > AllowedHostPaths< / em > 是 一 个 被 允 许 的 主 机 路 径 前 缀 的 白 名 单 。 空 值 表 示 所 有 的 主 机 路 径 都 可 以 使 用 。 < / li >
< / ul >
< h2 id = "许可" > 许 可 < / h2 >
< p > 包 含 < code > PodSecurityPolicy< / code > 的 < em > 许 可 控 制 < / em > ， 允 许 控 制 集 群 资 源 的 创 建 和 修 改 ， 基 于 这 些 资 源 在 集 群 范 围 内 被 许 可 的 能 力 。 < / p >
< p > 许 可 使 用 如 下 的 方 式 为 Pod 创 建 最 终 的 安 全 上 下 文 ： < / p >
< ol >
< li > 检 索 所 有 可 用 的 PSP。 < / li >
< li > 生 成 在 请 求 中 没 有 指 定 的 安 全 上 下 文 设 置 的 字 段 值 。 < / li >
< li > 基 于 可 用 的 策 略 ， 验 证 最 终 的 设 置 。 < / li >
< / ol >
< p > 如 果 某 个 策 略 能 够 匹 配 上 ， 该 Pod 就 被 接 受 。 如 果 请 求 与 PSP 不 匹 配 ， 则 Pod 被 拒 绝 。 < / p >
< p > Pod 必 须 基 于 PSP 验 证 每 个 字 段 。 < / p >
< h2 id = "创建-pod-安全策略" > 创 建 Pod 安 全 策 略 < / h2 >
< p > 下 面 是 一 个 Pod 安 全 策 略 的 例 子 ， 所 有 字 段 的 设 置 都 被 允 许 ： < / p >
< pre > < code class = "lang-Yaml" > < span class = "hljs-attr" > apiVersion:< / span > extensions/v1beta1
< span class = "hljs-attr" > kind:< / span > PodSecurityPolicy
< span class = "hljs-attr" > metadata:< / span >
< span class = "hljs-attr" > name:< / span > permissive
< span class = "hljs-attr" > spec:< / span >
< span class = "hljs-attr" > seLinux:< / span >
< span class = "hljs-attr" > rule:< / span > RunAsAny
< span class = "hljs-attr" > supplementalGroups:< / span >
< span class = "hljs-attr" > rule:< / span > RunAsAny
< span class = "hljs-attr" > runAsUser:< / span >
< span class = "hljs-attr" > rule:< / span > RunAsAny
< span class = "hljs-attr" > fsGroup:< / span >
< span class = "hljs-attr" > rule:< / span > RunAsAny
< span class = "hljs-attr" > hostPorts:< / span >
< span class = "hljs-attr" > - min:< / span > < span class = "hljs-number" > 8000< / span >
< span class = "hljs-attr" > max:< / span > < span class = "hljs-number" > 8080< / span >
< span class = "hljs-attr" > volumes:< / span >
< span class = "hljs-bullet" > -< / span > < span class = "hljs-string" > ' *' < / span >
< / code > < / pre >
< p > 下 载 示 例 文 件 可 以 创 建 该 策 略 ， 然 后 执 行 如 下 命 令 ： < / p >
< pre > < code class = "lang-bash" > $ kubectl create < span class = "hljs-_" > -f< / span > ./psp.yaml
podsecuritypolicy < span class = "hljs-string" > " permissive" < / span > created
< / code > < / pre >
< h2 id = "获取-pod-安全策略列表" > 获 取 Pod 安 全 策 略 列 表 < / h2 >
< p > 获 取 已 存 在 策 略 列 表 ， 使 用 < code > kubectl get< / code > ： < / p >
< pre > < code class = "lang-bash" > $ kubectl get psp
NAME PRIV CAPS SELINUX RUNASUSER FSGROUP SUPGROUP READONLYROOTFS VOLUMES
permissive < span class = "hljs-literal" > false< / span > [] RunAsAny RunAsAny RunAsAny RunAsAny < span class = "hljs-literal" > false< / span > [*]
privileged < span class = "hljs-literal" > true< / span > [] RunAsAny RunAsAny RunAsAny RunAsAny < span class = "hljs-literal" > false< / span > [*]
restricted < span class = "hljs-literal" > false< / span > [] RunAsAny MustRunAsNonRoot RunAsAny RunAsAny < span class = "hljs-literal" > false< / span > [emptyDir secret downwardAPI configMap persistentVolumeClaim projected]
< / code > < / pre >
< h2 id = "修改-pod-安全策略" > 修 改 Pod 安 全 策 略 < / h2 >
< p > 通 过 交 互 方 式 修 改 策 略 ， 使 用 < code > kubectl edit< / code > ： < / p >
< pre > < code class = "lang-bash" > $ kubectl edit psp permissive
< / code > < / pre >
< p > 该 命 令 将 打 开 一 个 默 认 文 本 编 辑 器 ， 在 这 里 能 够 修 改 策 略 。 < / p >
< h2 id = "删除-pod-安全策略" > 删 除 Pod 安 全 策 略 < / h2 >
< p > 一 旦 不 再 需 要 一 个 策 略 ， 很 容 易 通 过 < code > kubectl< / code > 删 除 它 ： < / p >
< pre > < code class = "lang-bash" > $ kubectl delete psp permissive
podsecuritypolicy < span class = "hljs-string" > " permissive" < / span > deleted
< / code > < / pre >
< h2 id = "启用-pod-安全策略" > 启 用 Pod 安 全 策 略 < / h2 >
< p > 为 了 能 够 在 集 群 中 使 用 Pod 安 全 策 略 ， 必 须 确 保 如 下 ： < / p >
< ol >
< li > 启 用 API 类 型 < code > extensions/v1beta1/podsecuritypolicy< / code > （ 仅 对 1.6 之 前 的 版 本 ） < / li >
< li > 启 用 许 可 控 制 器 < code > PodSecurityPolicy< / code > < / li >
< li > 定 义 自 己 的 策 略 < / li >
< / ol >
< h2 id = "使用-rbac" > 使 用 RBAC< / h2 >
< p > 在 Kubernetes 1.5 或 更 新 版 本 ， 可 以 使 用 PodSecurityPolicy 来 控 制 ， 对 基 于 用 户 角 色 和 组 的 已 授 权 容 器 的 访 问 。 访 问 不 同 的 PodSecurityPolicy 对 象 ， 可 以 基 于 认 证 来 控 制 。 基 于 Deployment、 ReplicaSet 等 创 建 的 Pod， 限 制 访 问 PodSecurityPolicy 对 象 ， < a href = "https://kubernetes.io/docs/admin/kube-controller-manager/" target = "_blank" > Controller Manager< / a > 必 须 基 于 安 全 API 端 口 运 行 ， 并 且 不 能 够 具 有 超 级 用 户 权 限 。 < / p >
< p > PodSecurityPolicy 认 证 使 用 所 有 可 用 的 策 略 ， 包 括 创 建 Pod 的 用 户 ， Pod 上 指 定 的 服 务 账 户 （ service acount） 。 当 Pod 基 于 Deployment、 ReplicaSet 创 建 时 ， 它 是 创 建 Pod 的 Controller Manager， 所 以 如 果 基 于 非 安 全 API 端 口 运 行 ， 允 许 所 有 的 PodSecurityPolicy 对 象 ， 并 且 不 能 够 有 效 地 实 现 细 分 权 限 。 用 户 访 问 给 定 的 PSP 策 略 有 效 ， 仅 当 是 直 接 部 署 Pod 的 情 况 。 更 多 详 情 ， 查 看 < a href = "https://git.k8s.io/kubernetes/examples/podsecuritypolicy/rbac/README.md" target = "_blank" > PodSecurityPolicy RBAC 示 例 < / a > ， 当 直 接 部 署 Pod 时 ， 应 用 PodSecurityPolicy 控 制 基 于 角 色 和 组 的 已 授 权 容 器 的 访 问 。 < / p >
< p > 原 文 地 址 ： < a href = "https://k8smeetup.github.io/docs/concepts/policy/pod-security-policy/" target = "_blank" > https://k8smeetup.github.io/docs/concepts/policy/pod-security-policy/< / a > < / p >
< p > 译 者 ： < a href = "https://github.com/shirdrn" target = "_blank" > shirdrn< / a > < / p >
< footer class = "page-footer-ex" > < span class = "page-footer-ex-copyright" > for GitBook< / span >                       < span class = "page-footer-ex-footer-update" > update
2017-09-03 14:07:37
< / span > < / footer >
< / section >
< / div >
< div class = "search-results" >
< div class = "has-results" >
< h1 class = "search-results-title" > < span class = 'search-results-count' > < / span > results matching "< span class = 'search-query' > < / span > "< / h1 >
< ul class = "search-results-list" > < / ul >
< / div >
< div class = "no-results" >
< h1 class = "search-results-title" > No results matching "< span class = 'search-query' > < / span > "< / h1 >
< / div >
< / div >
< / div >
< / div >
< / div >
< / div >
< a href = "init-containers.html" class = "navigation navigation-prev " aria-label = "Previous page: 2.2.1.2 Init容器" >
< i class = "fa fa-angle-left" > < / i >
< / a >
< a href = "node.html" class = "navigation navigation-next " aria-label = "Next page: 2.2.2 Node" >
< i class = "fa fa-angle-right" > < / i >
< / a >
< / div >
< script >
var gitbook = gitbook || [];
gitbook.push(function() {
2017-09-14 16:06:45 +08:00
gitbook.page.hasChanged({"page":{"title":"2.2.1.3 Pod安全策略","level":"1.2.2.1.3","depth":4,"next":{"title":"2.2.2 Node","level":"1.2.2.2","depth":3,"path":"concepts/node.md","ref":"concepts/node.md","articles":[]},"previous":{"title":"2.2.1.2 Init容器","level":"1.2.2.1.2","depth":4,"path":"concepts/init-containers.md","ref":"concepts/init-containers.md","articles":[]},"dir":"ltr"},"config":{"plugins":["github","codesnippet","splitter","page-toc-button","image-captions","page-footer-ex","editlink","-lunr","-search","search-plus"],"styles":{"website":"styles/website.css","pdf":"styles/pdf.css","epub":"styles/epub.css","mobi":"styles/mobi.css","ebook":"styles/ebook.css","print":"styles/print.css"},"pluginsConfig":{"github":{"url":"https://github.com/rootsongjc/kubernetes-handbook"},"editlink":{"label":"编辑本页","multilingual":false,"base":"https://github.com/rootsongjc/kubernetes-handbook/blob/master/"},"page-footer-ex":{"copyright":"for GitBook","update_format":"YYYY-MM-DD HH:mm:ss","update_label":"update"},"splitter":{},"codesnippet":{},"fontsettings":{"theme":"white","family":"sans","size":2},"highlight":{},"page-toc-button":{},"sharing":{"facebook":true,"twitter":true,"google":false,"weibo":false,"instapaper":false,"vk":false,"all":["facebook","google","twitter","weibo","instapaper"]},"theme-default":{"styles":{"website":"styles/website.css","pdf":"styles/pdf.css","epub":"styles/epub.css","mobi":"styles/mobi.css","ebook":"styles/ebook.css","print":"styles/print.css"},"showLevel":false},"search-plus":{},"image-captions":{"variable_name":"_pictures"}},"page-footer-ex":{"copyright":"Jimmy Song","update_label":"最后更新：","update_format":"YYYY-MM-DD HH:mm:ss"},"theme":"default","author":"Jimmy Song","pdf":{"pageNumbers":true,"fontSize":12,"fontFamily":"Arial","paperSize":"a4","chapterMark":"pagebreak","pageBreaksBefore":"/","margin":{"right":62,"left":62,"top":56,"bottom":56}},"structure":{"langs":"LANGS.md","readme":"README.md","glossary":"GLOSSARY.md","summary":"SUMMARY.md"},"variables":{"_pictures":[{"backlink":"concepts/index.html#fig1.2.1","level":"1.2","list_caption":"Figure: Borg架构","alt":"Borg架构","nro":1,"url":"../images/borg.png","index":1,"caption_template":"Figure: _CAPTION_","label":"Borg架构","attributes":{},"skip":false,"key":"1.2.1"},{"backlink":"concepts/index.html#fig1.2.2","level":"1.2","list_caption":"Figure: Kubernetes架构","alt":"Kubernetes架构","nro":2,"url":"../images/architecture.png","index":2,"caption_template":"Figure: _CAPTION_","label":"Kubernetes架构","attributes":{},"skip":false,"key":"1.2.2"},{"backlink":"concepts/index.html#fig1.2.3","level":"1.2","list_caption":"Figure: kubernetes整体架构示意图","alt":"kubernetes整体架构示意图","nro":3,"url":"../images/kubernetes-whole-arch.png","index":3,"caption_template":"Figure: _CAPTION_","label":"kubernetes整体架构示意图","attributes":{},"skip":false,"key":"1.2.3"},{"backlink":"concepts/index.html#fig1.2.4","level":"1.2","list_caption":"Figure: Kubernetes master架构示意图","alt":"Kubernetes master架构示意图","nro":4,"url":"../images/kubernetes-master-arch.png","index":4,"caption_template":"Figure: _CAPTION_","label":"Kubernetes master架构示意图","attributes":{},"skip":false,"key":"1.2.4"},{"backlink":"concepts/index.html#fig1.2.5","level":"1.2","list_caption":"Figure: kubernetes node架构示意图","alt":"kubernetes node架构示意图","nro":5,"url":"../images/kubernetes-node-arch.png","index":5,"caption_template":"Figure: _CAPTION_","label":"kubernetes node架构示意图","attributes":{},"skip":false,"key":"1.2.5"},{"backlink":"concepts/index.html#fig1.2.6","level":"1.2","list_caption":"Figure: Kubernetes分层架构示意图","alt":"Kubernetes分层架构示意图","nro":6,"url":"../images/kubernetes-layers-arch.jpg","index":6,"caption_template":"Figure: _CAPTION_","label":"Kubernetes分层架构示意图","attributes":{},"skip":false,"key":"1.2.6"},{"backlink":"concepts/concepts.html#fig1.2.1.1","level":"1.2.1","list_caption":"Figure: 分层架构示意图","alt"
2017-09-03 15:58:39 +08:00
});
< / script >
< / div >
< script src = "../gitbook/gitbook.js" > < / script >
< script src = "../gitbook/theme.js" > < / script >
< script src = "../gitbook/gitbook-plugin-github/plugin.js" > < / script >
< script src = "../gitbook/gitbook-plugin-splitter/splitter.js" > < / script >
< script src = "../gitbook/gitbook-plugin-page-toc-button/plugin.js" > < / script >
< script src = "../gitbook/gitbook-plugin-editlink/plugin.js" > < / script >
< script src = "../gitbook/gitbook-plugin-search-plus/jquery.mark.min.js" > < / script >
< script src = "../gitbook/gitbook-plugin-search-plus/search.js" > < / script >
< script src = "../gitbook/gitbook-plugin-sharing/buttons.js" > < / script >
< script src = "../gitbook/gitbook-plugin-fontsettings/fontsettings.js" > < / script >
< / body >
< / html >
