2017-08-21 17:44:43 +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 > 3.1.1 配置Pod的liveness和readiness探针 · 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 = "configure-pod-service-account.html" / >
< link rel = "prev" href = "resource-configuration.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" >
2017-09-03 13:29:38 +08:00
2.2 Objects
2017-08-21 17:44:43 +08:00
< / 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 >
2017-08-31 23:28:33 +08:00
< / 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 >
2017-09-03 15:58:39 +08:00
< / 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 >
2017-08-21 17:44:43 +08:00
< / 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 >
2017-09-03 15:58:39 +08:00
< / 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 >
2017-08-21 17:44:43 +08:00
< / li >
< / ul >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.3" data-path = "./" >
< a href = "./" >
3. 用户指南
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.3.1" data-path = "resource-configuration.html" >
< a href = "resource-configuration.html" >
3.1 资源配置
< / a >
< ul class = "articles" >
< li class = "chapter active" data-level = "1.3.1.1" data-path = "configure-liveness-readiness-probes.html" >
< a href = "configure-liveness-readiness-probes.html" >
3.1.1 配置Pod的liveness和readiness探针
< / a >
< / li >
< li class = "chapter " data-level = "1.3.1.2" data-path = "configure-pod-service-account.html" >
< a href = "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 = "command-usage.html" >
< a href = "command-usage.html" >
3.2 命令使用
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.3.2.1" data-path = "using-kubectl.html" >
< a href = "using-kubectl.html" >
3.2.1 使用kubectl
< / a >
2017-09-16 20:56:43 +08:00
< / li >
< li class = "chapter " data-level = "1.3.2.2" data-path = "docker-cli-to-kubectl.html" >
< a href = "docker-cli-to-kubectl.html" >
3.2.2 docker用户过度到kubectl命令行指南
< / a >
2017-08-21 17:44:43 +08:00
< / li >
< / ul >
< / li >
2017-09-07 12:29:13 +08:00
< li class = "chapter " data-level = "1.3.3" data-path = "cluster-security-management.html" >
2017-08-21 17:44:43 +08:00
2017-09-07 12:29:13 +08:00
< a href = "cluster-security-management.html" >
2017-08-21 17:44:43 +08:00
2017-09-07 12:29:13 +08:00
3.3 集群安全性管理
2017-08-21 17:44:43 +08:00
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.3.3.1" data-path = "managing-tls-in-a-cluster.html" >
< a href = "managing-tls-in-a-cluster.html" >
3.3.1 管理集群中的TLS
< / a >
2017-08-21 18:44:34 +08:00
< / li >
< li class = "chapter " data-level = "1.3.3.2" data-path = "kubelet-authentication-authorization.html" >
< a href = "kubelet-authentication-authorization.html" >
3.3.2 kubelet的认证授权
< / a >
< / li >
< li class = "chapter " data-level = "1.3.3.3" data-path = "tls-bootstrapping.html" >
< a href = "tls-bootstrapping.html" >
3.3.3 TLS bootstrap
< / a >
2017-08-31 14:23:44 +08:00
< / li >
< li class = "chapter " data-level = "1.3.3.4" data-path = "kubectl-user-authentication-authorization.html" >
< a href = "kubectl-user-authentication-authorization.html" >
3.3.4 kubectl的用户认证授权
< / a >
< / li >
< li class = "chapter " data-level = "1.3.3.5" data-path = "rbac.html" >
< a href = "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 = "ip-masq-agent.html" >
< a href = "ip-masq-agent.html" >
3.3.6 IP伪装代理
< / a >
2017-08-21 17:44:43 +08:00
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.3.4" data-path = "access-kubernetes-cluster.html" >
< a href = "access-kubernetes-cluster.html" >
3.4 访问 Kubernetes 集群
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.3.4.1" data-path = "access-cluster.html" >
< a href = "access-cluster.html" >
3.4.1 访问集群
< / a >
< / li >
< li class = "chapter " data-level = "1.3.4.2" data-path = "authenticate-across-clusters-kubeconfig.html" >
< a href = "authenticate-across-clusters-kubeconfig.html" >
3.4.2 使用 kubeconfig 文件配置跨集群认证
< / a >
< / li >
< li class = "chapter " data-level = "1.3.4.3" data-path = "connecting-to-applications-port-forward.html" >
< a href = "connecting-to-applications-port-forward.html" >
3.4.3 通过端口转发访问集群中的应用程序
< / a >
< / li >
< li class = "chapter " data-level = "1.3.4.4" data-path = "service-access-application-cluster.html" >
< a href = "service-access-application-cluster.html" >
3.4.4 使用 service 访问群集中的应用程序
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.3.5" data-path = "application-development-deployment-flow.html" >
< a href = "application-development-deployment-flow.html" >
3.5 在kubernetes中开发部署应用
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.3.5.1" data-path = "deploy-applications-in-kubernetes.html" >
< a href = "deploy-applications-in-kubernetes.html" >
3.5.1 适用于kubernetes的应用开发部署流程
< / a >
2017-08-21 18:44:34 +08:00
< / li >
< li class = "chapter " data-level = "1.3.5.2" data-path = "migrating-hadoop-yarn-to-kubernetes.html" >
< a href = "migrating-hadoop-yarn-to-kubernetes.html" >
3.5.2 迁移传统应用到kubernetes中——以Hadoop YARN为例
< / a >
2017-08-21 17:44:43 +08:00
< / 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 >
2017-09-03 15:58:39 +08:00
< / 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 >
2017-08-21 17:44:43 +08:00
< / 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 >
2017-09-01 21:04:51 +08:00
< / 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 >
2017-08-21 17:44:43 +08:00
< / 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" >
2017-08-30 14:20:52 +08:00
< li class = "chapter " data-level = "1.5.2.1" data-path = "../usecases/spark-standalone-on-kubernetes.html" >
2017-08-21 17:44:43 +08:00
2017-08-30 14:20:52 +08:00
< a href = "../usecases/spark-standalone-on-kubernetes.html" >
2017-08-21 17:44:43 +08:00
2017-08-30 14:20:52 +08:00
5.2.1 Spark standalone on Kubernetes
2017-08-21 17:44:43 +08:00
< / a >
2017-08-31 14:23:44 +08:00
< / 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-08-31 14:23:44 +08:00
2017-09-14 15:57:50 +08:00
< a href = "../usecases/running-spark-with-kubernetes-native-scheduler.html" >
2017-08-31 14:23:44 +08:00
5.2.2 运行支持kubernetes原生调度的Spark程序
< / a >
2017-08-21 17:44:43 +08:00
< / li >
< / ul >
2017-08-30 16:52:33 +08:00
< / li >
< li class = "chapter " data-level = "1.5.3" data-path = "../usecases/serverless.html" >
< a href = "../usecases/serverless.html" >
5.3 Serverless架构
< / a >
2017-08-21 17:44:43 +08:00
< / 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 = ".." > 3.1.1 配置Pod的liveness和readiness探针< / 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的liveness和readiness探针" > 配 置 Pod的 liveness和 readiness探 针 < / h1 >
< p > 当 你 使 用 kuberentes的 时 候 ， 有 没 有 遇 到 过 Pod在 启 动 后 一 会 就 挂 掉 然 后 又 重 新 启 动 这 样 的 恶 性 循 环 ？ 你 有 没 有 想 过 kubernetes是 如 何 检 测 pod是 否 还 存 活 ？ 虽 然 容 器 已 经 启 动 ， 但 是 kubernetes如 何 知 道 容 器 的 进 程 是 否 准 备 好 对 外 提 供 服 务 了 呢 ？ 让 我 们 通 过 kuberentes官 网 的 这 篇 文 章 < a href = "https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/" target = "_blank" > Configure Liveness and Readiness Probes< / a > ， 来 一 探 究 竟 。 < / p >
< p > 本 文 将 向 展 示 如 何 配 置 容 器 的 存 活 和 可 读 性 探 针 。 < / p >
< p > Kubelet使 用 liveness probe（ 存 活 探 针 ） 来 确 定 何 时 重 启 容 器 。 例 如 ， 当 应 用 程 序 处 于 运 行 状 态 但 无 法 做 进 一 步 操 作 ， liveness探 针 将 捕 获 到 deadlock， 重 启 处 于 该 状 态 下 的 容 器 ， 使 应 用 程 序 在 存 在 bug的 情 况 下 依 然 能 够 继 续 运 行 下 去 （ 谁 的 程 序 还 没 几 个 bug呢 ） 。 < / p >
< p > Kubelet使 用 readiness probe（ 就 绪 探 针 ） 来 确 定 容 器 是 否 已 经 就 绪 可 以 接 受 流 量 。 只 有 当 Pod中 的 容 器 都 处 于 就 绪 状 态 时 kubelet才 会 认 定 该 Pod处 于 就 绪 状 态 。 该 信 号 的 作 用 是 控 制 哪 些 Pod应 该 作 为 service的 后 端 。 如 果 Pod处 于 非 就 绪 状 态 ， 那 么 它 们 将 会 被 从 service的 load balancer中 移 除 。 < / p >
< h2 id = "定义-liveness命令" > 定 义 liveness命 令 < / h2 >
< p > 许 多 长 时 间 运 行 的 应 用 程 序 最 终 会 转 换 到 broken状 态 ， 除 非 重 新 启 动 ， 否 则 无 法 恢 复 。 Kubernetes提 供 了 liveness probe来 检 测 和 补 救 这 种 情 况 。 < / p >
< p > 在 本 次 练 习 将 基 于 < code > gcr.io/google_containers/busybox< / code > 镜 像 创 建 运 行 一 个 容 器 的 Pod。 以 下 是 Pod的 配 置 文 件 < code > exec-liveness.yaml< / code > ： < / 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" > labels:< / span >
< span class = "hljs-attr" > test:< / span > liveness
< span class = "hljs-attr" > name:< / span > liveness-exec
< span class = "hljs-attr" > spec:< / span >
< span class = "hljs-attr" > containers:< / span >
< span class = "hljs-attr" > - name:< / span > liveness
< span class = "hljs-attr" > args:< / span >
< span class = "hljs-bullet" > -< / span > /bin/sh
< span class = "hljs-bullet" > -< / span > -c
< span class = "hljs-bullet" > -< / span > touch /tmp/healthy; sleep < span class = "hljs-number" > 30< / span > ; rm -rf /tmp/healthy; sleep < span class = "hljs-number" > 600< / span >
< span class = "hljs-attr" > image:< / span > gcr.io/google_containers/busybox
< span class = "hljs-attr" > livenessProbe:< / span >
< span class = "hljs-attr" > exec:< / span >
< span class = "hljs-attr" > command:< / span >
< span class = "hljs-bullet" > -< / span > cat
< span class = "hljs-bullet" > -< / span > /tmp/healthy
< span class = "hljs-attr" > initialDelaySeconds:< / span > < span class = "hljs-number" > 5< / span >
< span class = "hljs-attr" > periodSeconds:< / span > < span class = "hljs-number" > 5< / span >
< / code > < / pre >
< p > 该 配 置 文 件 给 Pod配 置 了 一 个 容 器 。 < code > periodSeconds< / code > 规 定 kubelet要 每 隔 5秒 执 行 一 次 liveness probe。 < code > initialDelaySeconds< / code > 告 诉 kubelet在 第 一 次 执 行 probe之 前 要 的 等 待 5秒 钟 。 探 针 检 测 命 令 是 在 容 器 中 执 行 < code > cat /tmp/healthy< / code > 命 令 。 如 果 命 令 执 行 成 功 ， 将 返 回 0， kubelet就 会 认 为 该 容 器 是 活 着 的 并 且 很 健 康 。 如 果 返 回 非 0值 ， kubelet就 会 杀 掉 这 个 容 器 并 重 启 它 。 < / p >
< p > 容 器 启 动 时 ， 执 行 该 命 令 ： < / p >
< pre > < code class = "lang-shell" > /bin/sh -c " touch /tmp/healthy; sleep 30; rm -rf /tmp/healthy; sleep 600"
< / code > < / pre >
< p > 在 容 器 生 命 的 最 初 30秒 内 有 一 个 < code > /tmp/healthy< / code > 文 件 ， 在 这 30秒 内 < code > cat /tmp/healthy< / code > 命 令 会 返 回 一 个 成 功 的 返 回 码 。 30秒 后 ， < code > cat /tmp/healthy< / code > 将 返 回 失 败 的 返 回 码 。 < / p >
< p > 创 建 Pod： < / p >
< pre > < code class = "lang-shell" > kubectl create -f https://k8s.io/docs/tasks/configure-pod-container/exec-liveness.yaml
< / code > < / pre >
< p > 在 30秒 内 ， 查 看 Pod的 event： < / p >
< pre > < code > kubectl describe pod liveness-exec
< / code > < / pre > < p > 结 果 显 示 没 有 失 败 的 liveness probe： < / p >
< pre > < code class = "lang-shell" > FirstSeen LastSeen Count From SubobjectPath Type Reason Message
--------- -------- ----- ---- ------------- -------- ------ -------
24s 24s 1 {default-scheduler } Normal Scheduled Successfully assigned liveness-exec to worker0
23s 23s 1 {kubelet worker0} spec.containers{liveness} Normal Pulling pulling image " gcr.io/google_containers/busybox"
23s 23s 1 {kubelet worker0} spec.containers{liveness} Normal Pulled Successfully pulled image " gcr.io/google_containers/busybox"
23s 23s 1 {kubelet worker0} spec.containers{liveness} Normal Created Created container with docker id 86849c15382e; Security:[seccomp=unconfined]
23s 23s 1 {kubelet worker0} spec.containers{liveness} Normal Started Started container with docker id 86849c15382e
< / code > < / pre >
< p > 启 动 35秒 后 ， 再 次 查 看 pod的 event： < / p >
< pre > < code class = "lang-shell" > kubectl describe pod liveness-exec
< / code > < / pre >
< p > 在 最 下 面 有 一 条 信 息 显 示 liveness probe失 败 ， 容 器 被 删 掉 并 重 新 创 建 。 < / p >
< pre > < code class = "lang-shell" > FirstSeen LastSeen Count From SubobjectPath Type Reason Message
--------- -------- ----- ---- ------------- -------- ------ -------
37s 37s 1 {default-scheduler } Normal Scheduled Successfully assigned liveness-exec to worker0
36s 36s 1 {kubelet worker0} spec.containers{liveness} Normal Pulling pulling image " gcr.io/google_containers/busybox"
36s 36s 1 {kubelet worker0} spec.containers{liveness} Normal Pulled Successfully pulled image " gcr.io/google_containers/busybox"
36s 36s 1 {kubelet worker0} spec.containers{liveness} Normal Created Created container with docker id 86849c15382e; Security:[seccomp=unconfined]
36s 36s 1 {kubelet worker0} spec.containers{liveness} Normal Started Started container with docker id 86849c15382e
2s 2s 1 {kubelet worker0} spec.containers{liveness} Warning Unhealthy Liveness probe failed: cat: can' t open ' /tmp/healthy' : No such file or directory
< / code > < / pre >
< p > 再 等 30秒 ， 确 认 容 器 已 经 重 启 ： < / p >
< pre > < code class = "lang-shell" > kubectl get pod liveness-exec
< / code > < / pre >
< p > 从 输 出 结 果 来 < code > RESTARTS< / code > 值 加 1了 。 < / p >
< pre > < code class = "lang-shell" > NAME READY STATUS RESTARTS AGE
liveness-exec 1/1 Running 1 1m
< / code > < / pre >
< h2 id = "定义一个liveness-http请求" > 定 义 一 个 liveness HTTP请 求 < / h2 >
< p > 我 们 还 可 以 使 用 HTTP GET请 求 作 为 liveness probe。 下 面 是 一 个 基 于 < code > gcr.io/google_containers/liveness< / code > 镜 像 运 行 了 一 个 容 器 的 Pod的 例 子 < code > http-liveness.yaml< / code > ： < / 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" > labels:< / span >
< span class = "hljs-attr" > test:< / span > liveness
< span class = "hljs-attr" > name:< / span > liveness-http
< span class = "hljs-attr" > spec:< / span >
< span class = "hljs-attr" > containers:< / span >
< span class = "hljs-attr" > - name:< / span > liveness
< span class = "hljs-attr" > args:< / span >
< span class = "hljs-bullet" > -< / span > /server
< span class = "hljs-attr" > image:< / span > gcr.io/google_containers/liveness
< span class = "hljs-attr" > livenessProbe:< / span >
< span class = "hljs-attr" > httpGet:< / span >
< span class = "hljs-attr" > path:< / span > /healthz
< span class = "hljs-attr" > port:< / span > < span class = "hljs-number" > 8080< / span >
< span class = "hljs-attr" > httpHeaders:< / span >
< span class = "hljs-attr" > - name:< / span > X-Custom-Header
< span class = "hljs-attr" > value:< / span > Awesome
< span class = "hljs-attr" > initialDelaySeconds:< / span > < span class = "hljs-number" > 3< / span >
< span class = "hljs-attr" > periodSeconds:< / span > < span class = "hljs-number" > 3< / span >
< / code > < / pre >
< p > 该 配 置 文 件 只 定 义 了 一 个 容 器 ， < code > livenessProbe< / code > 指 定 kubelete需 要 每 隔 3秒 执 行 一 次 liveness probe。 < code > initialDelaySeconds< / code > 指 定 kubelet在 该 执 行 第 一 次 探 测 之 前 需 要 等 待 3秒 钟 。 该 探 针 将 向 容 器 中 的 server的 8080端 口 发 送 一 个 HTTP GET请 求 。 如 果 server的 < code > /healthz< / code > 路 径 的 handler返 回 一 个 成 功 的 返 回 码 ， kubelet就 会 认 定 该 容 器 是 活 着 的 并 且 很 健 康 。 如 果 返 回 失 败 的 返 回 码 ， kubelet将 杀 掉 该 容 器 并 重 启 它 。 < / p >
< p > 任 何 大 于 200小 于 400的 返 回 码 都 会 认 定 是 成 功 的 返 回 码 。 其 他 返 回 码 都 会 被 认 为 是 失 败 的 返 回 码 。 < / p >
< p > 查 看 该 server的 源 码 ： < a href = "http://k8s.io/docs/user-guide/liveness/image/server.go" target = "_blank" > server.go< / a > .< / p >
< p > 最 开 始 的 10秒 该 容 器 是 活 着 的 ， < code > /healthz< / code > handler返 回 200的 状 态 码 。 这 之 后 将 返 回 500的 返 回 码 。 < / p >
< pre > < code class = "lang-go" > http.HandleFunc(< span class = "hljs-string" > " /healthz" < / span > , < span class = "hljs-keyword" > func< / span > (w http.ResponseWriter, r *http.Request) {
duration := time.Now().Sub(started)
< span class = "hljs-keyword" > if< / span > duration.Seconds() > < span class = "hljs-number" > 10< / span > {
w.WriteHeader(< span class = "hljs-number" > 500< / span > )
w.Write([]< span class = "hljs-keyword" > byte< / span > (fmt.Sprintf(< span class = "hljs-string" > " error: %v" < / span > , duration.Seconds())))
} < span class = "hljs-keyword" > else< / span > {
w.WriteHeader(< span class = "hljs-number" > 200< / span > )
w.Write([]< span class = "hljs-keyword" > byte< / span > (< span class = "hljs-string" > " ok" < / span > ))
}
})
< / code > < / pre >
< p > 容 器 启 动 3秒 后 ， kubelet开 始 执 行 健 康 检 查 。 第 一 次 健 康 监 测 会 成 功 ， 但 是 10秒 后 ， 健 康 检 查 将 失 败 ， kubelet将 杀 掉 和 重 启 容 器 。 < / p >
< p > 创 建 一 个 Pod来 测 试 一 下 HTTP liveness检 测 ： < / p >
< pre > < code class = "lang-shell" > kubectl create -f https://k8s.io/docs/tasks/configure-pod-container/http-liveness.yaml
< / code > < / pre >
< p > After 10 seconds, view Pod events to verify that liveness probes have failed and
the Container has been restarted:< / p >
< p > 10秒 后 ， 查 看 Pod的 event， 确 认 liveness probe失 败 并 重 启 了 容 器 。 < / p >
< pre > < code class = "lang-shell" > kubectl describe pod liveness-http
< / code > < / pre >
< h2 id = "定义tcp-liveness探针" > 定 义 TCP liveness探 针 < / h2 >
< p > 第 三 种 liveness probe使 用 TCP Socket。 使 用 此 配 置 ， kubelet将 尝 试 在 指 定 端 口 上 打 开 容 器 的 套 接 字 。 如 果 可 以 建 立 连 接 ， 容 器 被 认 为 是 健 康 的 ， 如 果 不 能 就 认 为 是 失 败 的 。 < / 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 > goproxy
< span class = "hljs-attr" > labels:< / span >
< span class = "hljs-attr" > app:< / span > goproxy
< span class = "hljs-attr" > spec:< / span >
< span class = "hljs-attr" > containers:< / span >
< span class = "hljs-attr" > - name:< / span > goproxy
< span class = "hljs-attr" > image:< / span > gcr.io/google_containers/goproxy:< span class = "hljs-number" > 0.1< / span >
< span class = "hljs-attr" > ports:< / span >
< span class = "hljs-attr" > - containerPort:< / span > < span class = "hljs-number" > 8080< / span >
< span class = "hljs-attr" > readinessProbe:< / span >
< span class = "hljs-attr" > tcpSocket:< / span >
< span class = "hljs-attr" > port:< / span > < span class = "hljs-number" > 8080< / span >
< span class = "hljs-attr" > initialDelaySeconds:< / span > < span class = "hljs-number" > 5< / span >
< span class = "hljs-attr" > periodSeconds:< / span > < span class = "hljs-number" > 10< / span >
< span class = "hljs-attr" > livenessProbe:< / span >
< span class = "hljs-attr" > tcpSocket:< / span >
< span class = "hljs-attr" > port:< / span > < span class = "hljs-number" > 8080< / span >
< span class = "hljs-attr" > initialDelaySeconds:< / span > < span class = "hljs-number" > 15< / span >
< span class = "hljs-attr" > periodSeconds:< / span > < span class = "hljs-number" > 20< / span >
< / code > < / pre >
< p > 如 您 所 见 ， TCP检 查 的 配 置 与 HTTP检 查 非 常 相 似 。 此 示 例 同 时 使 用 了 readiness和 liveness probe。 容 器 启 动 后 5秒 钟 ， kubelet将 发 送 第 一 个 readiness probe。 这 将 尝 试 连 接 到 端 口 8080上 的 goproxy容 器 。 如 果 探 测 成 功 ， 则 该 pod将 被 标 记 为 就 绪 。 Kubelet将 每 隔 10秒 钟 执 行 一 次 该 检 查 。 < / p >
< p > 除 了 readiness probe之 外 ， 该 配 置 还 包 括 liveness probe。 容 器 启 动 15秒 后 ， kubelet将 运 行 第 一 个 liveness probe。 就 像 readiness probe一 样 ， 这 将 尝 试 连 接 到 goproxy容 器 上 的 8080端 口 。 如 果 liveness probe失 败 ， 容 器 将 重 新 启 动 。 < / p >
< h2 id = "使用命名的端口" > 使 用 命 名 的 端 口 < / h2 >
< p > 可 以 使 用 命 名 的 ContainerPort作 为 HTTP或 TCP liveness检 查 ： < / p >
< pre > < code class = "lang-yaml" > < span class = "hljs-attr" > ports:< / span >
< span class = "hljs-attr" > - name:< / span > liveness-port
< span class = "hljs-attr" > containerPort:< / span > < span class = "hljs-number" > 8080< / span >
< span class = "hljs-attr" > hostPort:< / span > < span class = "hljs-number" > 8080< / span >
< span class = "hljs-attr" > livenessProbe:< / span >
< span class = "hljs-attr" > httpGet:< / span >
< span class = "hljs-attr" > path:< / span > /healthz
< span class = "hljs-attr" > port:< / span > liveness-port
< / code > < / pre >
< h2 id = "定义readiness探针" > 定 义 readiness探 针 < / h2 >
< p > 有 时 ， 应 用 程 序 暂 时 无 法 对 外 部 流 量 提 供 服 务 。 例 如 ， 应 用 程 序 可 能 需 要 在 启 动 期 间 加 载 大 量 数 据 或 配 置 文 件 。 在 这 种 情 况 下 ， 你 不 想 杀 死 应 用 程 序 ， 但 你 也 不 想 发 送 请 求 。 Kubernetes提 供 了 readiness probe来 检 测 和 减 轻 这 些 情 况 。 Pod中 的 容 器 可 以 报 告 自 己 还 没 有 准 备 ， 不 能 处 理 Kubernetes服 务 发 送 过 来 的 流 量 。 < / p >
< p > Readiness probe的 配 置 跟 liveness probe很 像 。 唯 一 的 不 同 是 使 用 < code > readinessProbe< / code > 而 不 是 < code > livenessProbe< / code > 。 < / p >
< pre > < code class = "lang-yaml" > < span class = "hljs-attr" > readinessProbe:< / span >
< span class = "hljs-attr" > exec:< / span >
< span class = "hljs-attr" > command:< / span >
< span class = "hljs-bullet" > -< / span > cat
< span class = "hljs-bullet" > -< / span > /tmp/healthy
< span class = "hljs-attr" > initialDelaySeconds:< / span > < span class = "hljs-number" > 5< / span >
< span class = "hljs-attr" > periodSeconds:< / span > < span class = "hljs-number" > 5< / span >
< / code > < / pre >
< p > Readiness probe的 HTTP和 TCP的 探 测 器 配 置 跟 liveness probe一 样 。 < / p >
< p > Readiness和 livenss probe可 以 并 行 用 于 同 一 容 器 。 使 用 两 者 可 以 确 保 流 量 无 法 到 达 未 准 备 好 的 容 器 ， 并 且 容 器 在 失 败 时 重 新 启 动 。 < / p >
< h2 id = "配置probe" > 配 置 Probe< / h2 >
< p > < a href = "https://kubernetes.io/docs/api-reference/v1.6/#probe-v1-core" target = "_blank" > Probe< / a > 中 有 很 多 精 确 和 详 细 的 配 置 ， 通 过 它 们 你 能 准 确 的 控 制 liveness和 readiness检 查 ： < / p >
< ul >
< li > < code > initialDelaySeconds< / code > ： 容 器 启 动 后 第 一 次 执 行 探 测 是 需 要 等 待 多 少 秒 。 < / li >
< li > < code > periodSeconds< / code > ： 执 行 探 测 的 频 率 。 默 认 是 10秒 ， 最 小 1秒 。 < / li >
< li > < code > timeoutSeconds< / code > ： 探 测 超 时 时 间 。 默 认 1秒 ， 最 小 1秒 。 < / li >
< li > < code > successThreshold< / code > ： 探 测 失 败 后 ， 最 少 连 续 探 测 成 功 多 少 次 才 被 认 定 为 成 功 。 默 认 是 1。 对 于 liveness必 须 是 1。 最 小 值 是 1。 < / li >
< li > < code > failureThreshold< / code > ： 探 测 成 功 后 ， 最 少 连 续 探 测 失 败 多 少 次 才 被 认 定 为 失 败 。 默 认 是 3。 最 小 值 是 1。 < / li >
< / ul >
< p > < a href = "https://kubernetes.io/docs/api-reference/v1.6/#httpgetaction-v1-core" target = "_blank" > HTTP probe< / a > 中 可 以 给 < code > httpGet< / code > 设 置 其 他 配 置 项 ： < / p >
< ul >
< li > < code > host< / code > ： 连 接 的 主 机 名 ， 默 认 连 接 到 pod的 IP。 你 可 能 想 在 http header中 设 置 " Host" 而 不 是 使 用 IP。 < / li >
< li > < code > scheme< / code > ： 连 接 使 用 的 schema， 默 认 HTTP。 < / li >
< li > < code > path< / code > : 访 问 的 HTTP server的 path。 < / li >
< li > < code > httpHeaders< / code > ： 自 定 义 请 求 的 header。 HTTP运 行 重 复 的 header。 < / li >
< li > < code > port< / code > ： 访 问 的 容 器 的 端 口 名 字 或 者 端 口 号 。 端 口 号 必 须 介 于 1和 65525之 间 。 < / li >
< / ul >
< p > 对 于 HTTP探 测 器 ， kubelet向 指 定 的 路 径 和 端 口 发 送 HTTP请 求 以 执 行 检 查 。 Kubelet将 probe发 送 到 容 器 的 IP地 址 ， 除 非 地 址 被 < code > httpGet< / code > 中 的 可 选 < code > host< / code > 字 段 覆 盖 。 在 大 多 数 情 况 下 ， 你 不 想 设 置 主 机 字 段 。 有 一 种 情 况 下 你 可 以 设 置 它 。 假 设 容 器 在 127.0.0.1上 侦 听 ， 并 且 Pod的 < code > hostNetwork< / code > 字 段 为 true。 然 后 ， 在 < code > httpGet< / code > 下 的 < code > host< / code > 应 该 设 置 为 127.0.0.1。 如 果 你 的 pod依 赖 于 虚 拟 主 机 ， 这 可 能 是 更 常 见 的 情 况 ， 你 不 应 该 是 用 < code > host< / code > ， 而 是 应 该 在 < code > httpHeaders< / code > 中 设 置 < code > Host< / code > 头 。 < / p >
< h2 id = "参考" > 参 考 < / h2 >
< ul >
< li > 关 于 < a href = "../docs/concepts/workloads/pods/pod-lifecycle#container-probes" > Container Probes< / a > 的 更 多 信 息 < / li >
< / ul >
< footer class = "page-footer-ex" > < span class = "page-footer-ex-copyright" > for GitBook< / span >                       < span class = "page-footer-ex-footer-update" > update
2017-08-21 18:44:34 +08:00
2017-08-21 18:23:34
2017-08-21 17:44:43 +08:00
< / 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 = "resource-configuration.html" class = "navigation navigation-prev " aria-label = "Previous page: 3.1 资源配置" >
< i class = "fa fa-angle-left" > < / i >
< / a >
< a href = "configure-pod-service-account.html" class = "navigation navigation-next " aria-label = "Next page: 3.1.2 配置Pod的Service Account" >
< i class = "fa fa-angle-right" > < / i >
< / a >
< / div >
< script >
var gitbook = gitbook || [];
gitbook.push(function() {
2017-09-16 20:56:43 +08:00
gitbook.page.hasChanged({"page":{"title":"3.1.1 配置Pod的liveness和readiness探针","level":"1.3.1.1","depth":3,"next":{"title":"3.1.2 配置Pod的Service Account","level":"1.3.1.2","depth":3,"path":"guide/configure-pod-service-account.md","ref":"guide/configure-pod-service-account.md","articles":[]},"previous":{"title":"3.1 资源配置","level":"1.3.1","depth":2,"path":"guide/resource-configuration.md","ref":"guide/resource-configuration.md","articles":[{"title":"3.1.1 配置Pod的liveness和readiness探针","level":"1.3.1.1","depth":3,"path":"guide/configure-liveness-readiness-probes.md","ref":"guide/configure-liveness-readiness-probes.md","articles":[]},{"title":"3.1.2 配置Pod的Service Account","level":"1.3.1.2","depth":3,"path":"guide/configure-pod-service-account.md","ref":"guide/configure-pod-service-account.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":fal
2017-08-21 17:44:43 +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 >
