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 > 4.3.7 管理容器的计算资源 · 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 = "storage.html" / >
< link rel = "prev" href = "data-persistence-problem.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 = "../concepts/" >
< a href = "../concepts/" >
2. 概念原理
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.2.1" data-path = "../concepts/concepts.html" >
< a href = "../concepts/concepts.html" >
2.1 设计理念
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2" data-path = "../concepts/objects.html" >
< a href = "../concepts/objects.html" >
2.2 Objects
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.2.2.1" data-path = "../concepts/pod-overview.html" >
< a href = "../concepts/pod-overview.html" >
2.2.1 Pod
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.2.2.1.1" data-path = "../concepts/pod.html" >
< a href = "../concepts/pod.html" >
2.2.1.1 Pod解析
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.1.2" data-path = "../concepts/init-containers.html" >
< a href = "../concepts/init-containers.html" >
2.2.1.2 Init容器
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.1.3" data-path = "../concepts/pod-security-policy.html" >
< a href = "../concepts/pod-security-policy.html" >
2.2.1.3 Pod安全策略
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.2.2.2" data-path = "../concepts/node.html" >
< a href = "../concepts/node.html" >
2.2.2 Node
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.3" data-path = "../concepts/namespace.html" >
< a href = "../concepts/namespace.html" >
2.2.3 Namespace
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.4" data-path = "../concepts/service.html" >
< a href = "../concepts/service.html" >
2.2.4 Service
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.5" data-path = "../concepts/volume.html" >
< a href = "../concepts/volume.html" >
2.2.5 Volume和Persistent Volume
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.6" data-path = "../concepts/deployment.html" >
< a href = "../concepts/deployment.html" >
2.2.6 Deployment
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.7" data-path = "../concepts/secret.html" >
< a href = "../concepts/secret.html" >
2.2.7 Secret
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.8" data-path = "../concepts/statefulset.html" >
< a href = "../concepts/statefulset.html" >
2.2.8 StatefulSet
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.9" data-path = "../concepts/daemonset.html" >
< a href = "../concepts/daemonset.html" >
2.2.9 DaemonSet
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.10" data-path = "../concepts/serviceaccount.html" >
< a href = "../concepts/serviceaccount.html" >
2.2.10 ServiceAccount
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.11" data-path = "../concepts/replicaset.html" >
< a href = "../concepts/replicaset.html" >
2.2.11 ReplicationController和ReplicaSet
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.12" data-path = "../concepts/job.html" >
< a href = "../concepts/job.html" >
2.2.12 Job
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.13" data-path = "../concepts/cronjob.html" >
< a href = "../concepts/cronjob.html" >
2.2.13 CronJob
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.14" data-path = "../concepts/ingress.html" >
< a href = "../concepts/ingress.html" >
2.2.14 Ingress
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.15" data-path = "../concepts/configmap.html" >
< a href = "../concepts/configmap.html" >
2.2.15 ConfigMap
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.16" data-path = "../concepts/horizontal-pod-autoscaling.html" >
< a href = "../concepts/horizontal-pod-autoscaling.html" >
2.2.16 Horizontal Pod Autoscaling
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.17" data-path = "../concepts/label.html" >
< a href = "../concepts/label.html" >
2.2.17 Label
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.18" data-path = "../concepts/garbage-collection.html" >
< a href = "../concepts/garbage-collection.html" >
2.2.18 垃圾收集
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.19" data-path = "../concepts/network-policy.html" >
< a href = "../concepts/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 >
< li class = "chapter " data-level = "1.3.3" data-path = "../guide/cluster-management.html" >
< a href = "../guide/cluster-management.html" >
3.3 集群管理
< / 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 >
< / 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 = "./" >
< a href = "./" >
4. 最佳实践
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.4.1" data-path = "install-kbernetes1.6-on-centos.html" >
< a href = "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 = "create-tls-and-secret-key.html" >
< a href = "create-tls-and-secret-key.html" >
4.1.1 创建TLS证书和秘钥
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.2" data-path = "create-kubeconfig.html" >
< a href = "create-kubeconfig.html" >
4.1.2 创建kubeconfig文件
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.3" data-path = "etcd-cluster-installation.html" >
< a href = "etcd-cluster-installation.html" >
4.1.3 创建高可用etcd集群
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.4" data-path = "kubectl-installation.html" >
< a href = "kubectl-installation.html" >
4.1.4 安装kubectl命令行工具
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.5" data-path = "master-installation.html" >
< a href = "master-installation.html" >
4.1.5 部署master节点
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.6" data-path = "node-installation.html" >
< a href = "node-installation.html" >
4.1.6 部署node节点
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.7" data-path = "kubedns-addon-installation.html" >
< a href = "kubedns-addon-installation.html" >
4.1.7 安装kubedns插件
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.8" data-path = "dashboard-addon-installation.html" >
< a href = "dashboard-addon-installation.html" >
4.1.8 安装dashboard插件
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.9" data-path = "heapster-addon-installation.html" >
< a href = "heapster-addon-installation.html" >
4.1.9 安装heapster插件
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.10" data-path = "efk-addon-installation.html" >
< a href = "efk-addon-installation.html" >
4.1.10 安装EFK插件
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.4.2" data-path = "service-discovery-and-loadbalancing.html" >
< a href = "service-discovery-and-loadbalancing.html" >
4.2 服务发现与负载均衡
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.4.2.1" data-path = "traefik-ingress-installation.html" >
< a href = "traefik-ingress-installation.html" >
4.2.1 安装Traefik ingress
< / a >
< / li >
< li class = "chapter " data-level = "1.4.2.2" data-path = "distributed-load-test.html" >
< a href = "distributed-load-test.html" >
4.2.2 分布式负载测试
< / a >
< / li >
< li class = "chapter " data-level = "1.4.2.3" data-path = "network-and-cluster-perfermance-test.html" >
< a href = "network-and-cluster-perfermance-test.html" >
4.2.3 网络和集群性能测试
< / a >
< / li >
< li class = "chapter " data-level = "1.4.2.4" data-path = "edge-node-configuration.html" >
< a href = "edge-node-configuration.html" >
4.2.4 边缘节点配置
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.4.3" data-path = "operation.html" >
< a href = "operation.html" >
4.3 运维管理
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.4.3.1" data-path = "service-rolling-update.html" >
< a href = "service-rolling-update.html" >
4.3.1 服务滚动升级
< / a >
< / li >
< li class = "chapter " data-level = "1.4.3.2" data-path = "app-log-collection.html" >
< a href = "app-log-collection.html" >
4.3.2 应用日志收集
< / a >
< / li >
< li class = "chapter " data-level = "1.4.3.3" data-path = "configuration-best-practice.html" >
< a href = "configuration-best-practice.html" >
4.3.3 配置最佳实践
< / a >
< / li >
< li class = "chapter " data-level = "1.4.3.4" data-path = "monitor.html" >
< a href = "monitor.html" >
4.3.4 集群及应用监控
< / a >
< / li >
< li class = "chapter " data-level = "1.4.3.5" data-path = "jenkins-ci-cd.html" >
< a href = "jenkins-ci-cd.html" >
4.3.5 使用Jenkins进行持续构建与发布
< / a >
< / li >
< li class = "chapter " data-level = "1.4.3.6" data-path = "data-persistence-problem.html" >
< a href = "data-persistence-problem.html" >
4.3.6 数据持久化问题
< / a >
< / li >
< li class = "chapter active" data-level = "1.4.3.7" data-path = "manage-compute-resources-container.html" >
< a href = "manage-compute-resources-container.html" >
4.3.7 管理容器的计算资源
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.4.4" data-path = "storage.html" >
< a href = "storage.html" >
4.4 存储管理
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.4.4.1" data-path = "glusterfs.html" >
< a href = "glusterfs.html" >
4.4.1 GlusterFS
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.4.4.1.1" data-path = "using-glusterfs-for-persistent-storage.html" >
< a href = "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 = "storage-for-containers-using-glusterfs-with-openshift.html" >
< a href = "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 = "cephfs.html" >
< a href = "cephfs.html" >
4.4.2 CephFS
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.4.4.2.1" data-path = "using-ceph-for-persistent-storage.html" >
< a href = "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 >
< li class = "chapter " data-level = "1.5.2.2" data-path = "../usecases/support-spark-natively-in-kubernetes.html" >
< a href = "../usecases/support-spark-natively-in-kubernetes.html" >
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 = ".." > 4.3.7 管理容器的计算资源< / 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 = "管理容器的计算资源" > 管 理 容 器 的 计 算 资 源 < / h1 >
< p > 当 您 定 义 < a href = "http://kubernetes.io/docks/user-guide/pods" target = "_blank" > Pod< / a > 的 时 候 可 以 选 择 为 每 个 容 器 指 定 需 要 的 CPU 和 内 存 （ RAM） 大 小 。 当 为 容 器 指 定 了 资 源 请 求 后 ， 调 度 器 就 能 够 更 好 的 判 断 出 将 容 器 调 度 到 哪 个 节 点 上 。 如 果 您 还 为 容 器 指 定 了 资 源 限 制 ， 节 点 上 的 资 源 就 可 以 按 照 指 定 的 方 式 做 竞 争 。 关 于 资 源 请 求 和 限 制 的 不 同 点 和 更 多 资 料 请 参 考 < a href = "https://git.k8s.io/community/contributors/design-proposals/resource-qos.md" target = "_blank" > Resource QoS< / a > 。 < / p >
< h2 id = "资源类型" > 资 源 类 型 < / h2 >
< p > < em > CPU< / em > 和 < em > memory< / em > 都 是 < em > 资 源 类 型 < / em > 。 资 源 类 型 具 有 基 本 单 位 。 CPU 的 单 位 是 core， memory 的 单 位 是 byte。 < / p >
< p > CPU和 内 存 统 称 为 < em > 计 算 资 源 < / em > ， 也 可 以 称 为 < em > 资 源 < / em > 。 计 算 资 源 的 数 量 是 可 以 被 请 求 、 分 配 和 消 耗 的 可 测 量 的 。 它 们 与 < a href = "https://kubernetes.io/docks/api/" target = "_blank" > API 资 源 < / a > 不 同 。 API 资 源 （ 如 Pod 和 < a href = "https://kubernetes.io/docks/user-guide/services" target = "_blank" > Service< / a > ） 是 可 通 过 Kubernetes API server 读 取 和 修 改 的 对 象 。 < / p >
< h2 id = "pod-和-容器的资源请求和限制" > Pod 和 容 器 的 资 源 请 求 和 限 制 < / h2 >
< p > Pod 中 的 每 个 容 器 都 可 以 指 定 以 下 的 一 个 或 者 多 个 值 ： < / p >
< ul >
< li > spec.containers[].resources.limits.cpu`< / li >
< li > < code > spec.containers[].resources.limits.memory< / code > < / li >
< li > < code > spec.containers[].resources.requests.cpu< / code > < / li >
< li > < code > spec.containers[].resources.requests.memory< / code > < / li >
< / ul >
< p > 尽 管 只 能 在 个 别 容 器 上 指 定 请 求 和 限 制 ， 但 是 我 们 可 以 方 便 地 计 算 出 Pod 资 源 请 求 和 限 制 。 特 定 资 源 类 型 的 Pod 资 源 请 求 /限 制 是 Pod 中 每 个 容 器 的 该 类 型 的 资 源 请 求 /限 制 的 总 和 。 < / p >
< h2 id = "cpu-的含义" > CPU 的 含 义 < / h2 >
< p > CPU 资 源 的 限 制 和 请 求 以 < em > cpu< / em > 为 单 位 。 < / p >
< p > Kubernetes 中 的 一 个 cpu 等 于 ： < / p >
< ul >
< li > 1 AWS vCPU< / li >
< li > 1 GCP Core< / li >
< li > 1 Azure vCore< / li >
< li > 1 < em > Hyperthread< / em > 在 带 有 超 线 程 的 裸 机 Intel 处 理 器 上 < / li >
< / ul >
< p > 允 许 浮 点 数 请 求 。 具 有 < code > spec.containers[].resources.requests.cpu< / code > 为 0.5 的 容 器 保 证 了 一 半 CPU 要 求 1 CPU的 一 半 。 表 达 式 < code > 0.1< / code > 等 价 于 表 达 式 < code > 100m< / code > ， 可 以 看 作 “ 100 millicpu” 。 有 些 人 说 成 是 “ 一 百 毫 cpu” ， 其 实 说 的 是 同 样 的 事 情 。 具 有 小 数 点 （ 如 < code > 0.1< / code > ） 的 请 求 由 API 转 换 为 < code > 100m< / code > ， 精 度 不 超 过 < code > 1m< / code > 。 因 此 ， 可 能 会 优 先 选 择 < code > 100m< / code > 的 形 式 。 < / p >
< h2 id = "内存的含义" > 内 存 的 含 义 < / h2 >
< p > 内 存 的 限 制 和 请 求 以 字 节 为 单 位 。 您 可 以 使 用 以 下 后 缀 之 一 作 为 平 均 整 数 或 定 点 整 数 表 示 内 存 ： E， P， T， G， M， K。 您 还 可 以 使 用 两 个 字 母 的 等 效 的 幂 数 ： Ei， Pi， Ti ， Gi， Mi， Ki。 例 如 ， 以 下 代 表 大 致 相 同 的 值 ： < / p >
< pre > < code class = "lang-shell" > 128974848, 129e6, 129M, 123Mi
< / code > < / pre >
< p > 下 面 是 个 例 子 。 < / p >
< p > 以 下 Pod 有 两 个 容 器 。 每 个 容 器 的 请 求 为 0.25 cpu 和 64MiB（ 2< sup > 26< / sup > ） 内 存 ， 每 个 容 器 的 限 制 为 0.5 cpu 和 128MiB 内 存 。 您 可 以 说 该 Pod 请 求 0.5 cpu 和 128 MiB 的 内 存 ， 限 制 为 1 cpu 和 256MiB 的 内 存 。 < / p >
< pre > < code class = "lang-yaml" > < span class = "hljs-attr" > apiVersion:< / span > v1
< span class = "hljs-attr" > kind:< / span > Pod
< span class = "hljs-attr" > metadata:< / span >
< span class = "hljs-attr" > name:< / span > frontend
< span class = "hljs-attr" > spec:< / span >
< span class = "hljs-attr" > containers:< / span >
< span class = "hljs-attr" > - name:< / span > db
< span class = "hljs-attr" > image:< / span > mysql
< span class = "hljs-attr" > resources:< / span >
< span class = "hljs-attr" > requests:< / span >
< span class = "hljs-attr" > memory:< / span > < span class = "hljs-string" > " 64Mi" < / span >
< span class = "hljs-attr" > cpu:< / span > < span class = "hljs-string" > " 250m" < / span >
< span class = "hljs-attr" > limits:< / span >
< span class = "hljs-attr" > memory:< / span > < span class = "hljs-string" > " 128Mi" < / span >
< span class = "hljs-attr" > cpu:< / span > < span class = "hljs-string" > " 500m" < / span >
< span class = "hljs-attr" > - name:< / span > wp
< span class = "hljs-attr" > image:< / span > wordpress
< span class = "hljs-attr" > resources:< / span >
< span class = "hljs-attr" > requests:< / span >
< span class = "hljs-attr" > memory:< / span > < span class = "hljs-string" > " 64Mi" < / span >
< span class = "hljs-attr" > cpu:< / span > < span class = "hljs-string" > " 250m" < / span >
< span class = "hljs-attr" > limits:< / span >
< span class = "hljs-attr" > memory:< / span > < span class = "hljs-string" > " 128Mi" < / span >
< span class = "hljs-attr" > cpu:< / span > < span class = "hljs-string" > " 500m" < / span >
< / code > < / pre >
< h2 id = "具有资源请求的-pod-如何调度" > 具 有 资 源 请 求 的 Pod 如 何 调 度 < / h2 >
< p > 当 您 创 建 一 个 Pod 时 ， Kubernetes 调 度 程 序 将 为 Pod 选 择 一 个 节 点 。 每 个 节 点 具 有 每 种 资 源 类 型 的 最 大 容 量 ： 可 为 Pod 提 供 的 CPU 和 内 存 量 。 调 度 程 序 确 保 对 于 每 种 资 源 类 型 ， 调 度 的 容 器 的 资 源 请 求 的 总 和 小 于 节 点 的 容 量 。 请 注 意 ， 尽 管 节 点 上 的 实 际 内 存 或 CPU 资 源 使 用 量 非 常 低 ， 但 如 果 容 量 检 查 失 败 ， 则 调 度 程 序 仍 然 拒 绝 在 该 节 点 上 放 置 Pod。 当 资 源 使 用 量 稍 后 增 加 时 ， 例 如 在 请 求 率 的 每 日 峰 值 期 间 ， 这 可 以 防 止 节 点 上 的 资 源 短 缺 。 < / p >
< h2 id = "具有资源限制的-pod-如何运行" > 具 有 资 源 限 制 的 Pod 如 何 运 行 < / h2 >
< p > 当 kubelet 启 动 一 个 Pod 的 容 器 时 ， 它 会 将 CPU 和 内 存 限 制 传 递 到 容 器 运 行 时 。 < / p >
< p > 当 使 用 Docker 时 ： < / p >
< ul >
< li > < code > spec.containers[].resources.requests.cpu< / code > 的 值 将 转 换 成 core 值 ， 这 是 个 浮 点 数 ， 并 乘 以 1024， 这 个 数 字 中 的 较 大 者 或 2用 作 < code > docker run< / code > 命 令 中 的 < a href = "https://docs.docker.com/engine/reference/run/#/cpu-share-constraint" target = "_blank" > < code > --cpu-shares< / code > < / a > 标 志 的 值 。 < / li >
< li > < code > spec.containers[].resources.limits.cpu< / code > 被 转 换 成 millicore 值 。 被 乘 以 100000 然 后 除 以 1000。 这 个 数 字 用 作 < code > docker run< / code > 命 令 中 的 < a href = "https://docs.docker.com/engine/reference/run/#/cpu-quota-constraint" target = "_blank" > < code > --cpu-quota< / code > < / a > 标 志 的 值 。 [< code > --cpu-quota< / code > ] 标 志 被 设 置 成 了 100000， 表 示 测 量 配 额 使 用 的 默 认 100ms 周 期 。 如 果 [< code > --cpu-cfs-quota< / code > ] 标 志 设 置 为 true， 则 kubelet 会 强 制 执 行 cpu 限 制 。 从 Kubernetes 1.2 版 本 起 ， 此 标 志 默 认 为 true。 < / li >
< li > < code > spec.containers[].resources.limits.memory< / code > 被 转 换 为 整 型 ， 作 为 < code > docker run< / code > 命 令 中 的 < a href = "https://docs.docker.com/engine/reference/run/#/user-memory-constraints" target = "_blank" > < code > --memory< / code > < / a > 标 志 的 值 。 < / li >
< / ul >
< p > 如 果 容 器 超 过 其 内 存 限 制 ， 则 可 能 会 被 终 止 。 如 果 可 重 新 启 动 ， 则 与 所 有 其 他 类 型 的 运 行 时 故 障 一 样 ， kubelet 将 重 新 启 动 它 。 < / p >
< p > 如 果 一 个 容 器 超 过 其 内 存 请 求 ， 那 么 当 节 点 内 存 不 足 时 ， 它 的 Pod 可 能 被 逐 出 。 < / p >
< p > 容 器 可 能 被 允 许 也 可 能 不 被 允 许 超 过 其 CPU 限 制 时 间 。 但 是 ， 由 于 CPU 使 用 率 过 高 ， 不 会 被 杀 死 。 < / p >
< p > 要 确 定 容 器 是 否 由 于 资 源 限 制 而 无 法 安 排 或 被 杀 死 ， 请 参 阅 < a href = "#troubleshooting" > 疑 难 解 答 < / a > 部 分 。 < / p >
< h2 id = "监控计算资源使用" > 监 控 计 算 资 源 使 用 < / h2 >
< p > Pod 的 资 源 使 用 情 况 被 报 告 为 Pod 状 态 的 一 部 分 。 < / p >
< p > 如 果 为 集 群 配 置 了 < a href = "http://releases.k8s.io//cluster/addons/cluster-monitoring/README.md" target = "_blank" > 可 选 监 控 < / a > ， 则 可 以 从 监 视 系 统 检 索 Pod 资 源 的 使 用 情 况 。 < / p >
< h2 id = "疑难解答" > 疑 难 解 答 < / h2 >
< 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 15:56:45
< / 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 = "data-persistence-problem.html" class = "navigation navigation-prev " aria-label = "Previous page: 4.3.6 数据持久化问题" >
< i class = "fa fa-angle-left" > < / i >
< / a >
< a href = "storage.html" class = "navigation navigation-next " aria-label = "Next page: 4.4 存储管理" >
< i class = "fa fa-angle-right" > < / i >
< / a >
< / div >
< script >
var gitbook = gitbook || [];
gitbook.push(function() {
2017-09-04 19:34:11 +08:00
gitbook.page.hasChanged({"page":{"title":"4.3.7 管理容器的计算资源","level":"1.4.3.7","depth":3,"next":{"title":"4.4 存储管理","level":"1.4.4","depth":2,"path":"practice/storage.md","ref":"practice/storage.md","articles":[{"title":"4.4.1 GlusterFS","level":"1.4.4.1","depth":3,"path":"practice/glusterfs.md","ref":"practice/glusterfs.md","articles":[{"title":"4.4.1.1 使用GlusterFS做持久化存储","level":"1.4.4.1.1","depth":4,"path":"practice/using-glusterfs-for-persistent-storage.md","ref":"practice/using-glusterfs-for-persistent-storage.md","articles":[]},{"title":"4.4.1.2 在OpenShift中使用GlusterFS做持久化存储","level":"1.4.4.1.2","depth":4,"path":"practice/storage-for-containers-using-glusterfs-with-openshift.md","ref":"practice/storage-for-containers-using-glusterfs-with-openshift.md","articles":[]}]},{"title":"4.4.2 CephFS","level":"1.4.4.2","depth":3,"path":"practice/cephfs.md","ref":"practice/cephfs.md","articles":[{"title":"4.4.2.1 使用Ceph做持久化存储","level":"1.4.4.2.1","depth":4,"path":"practice/using-ceph-for-persistent-storage.md","ref":"practice/using-ceph-for-persistent-storage.md","articles":[]}]}]},"previous":{"title":"4.3.6 数据持久化问题","level":"1.4.3.6","depth":3,"path":"practice/data-persistence-problem.md","ref":"practice/data-persistence-problem.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,"u
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 >
