1. Bookinfo应用与Kubernetes部署背景Bookinfo是Istio官方提供的示例微服务应用由四个独立服务组成productpage前端页面、details书籍详情、reviews书评服务和ratings评分服务。这个看似简单的应用实际上包含了微服务架构的典型特征——多语言开发Python/Java/Ruby/Node.js、服务间调用链以及版本化部署需求。在Kubernetes中部署Bookinfo的价值在于它是学习Service Mesh技术的标准实验对象完整的YAML配置涵盖了K8s部署的各类资源类型可扩展为灰度发布、流量管理等高级场景的测试平台官方维护保证了配置的规范性和兼容性我首次接触这个案例是在2018年做Istio技术预研时当时为了调试一个Ingress路由问题花了整整三天时间反复修改YAML文件。这段经历让我深刻认识到看似简单的示例应用其部署配置中藏着无数魔鬼细节。2. 部署环境准备与前置检查2.1 基础环境要求在开始编写YAML之前需要确保环境满足以下条件# 验证Kubernetes集群状态 kubectl cluster-info kubectl get nodes -o wide # 检查存储类是否可用部分配置需要PVC kubectl get storageclass # 确认网络插件正常工作 kubectl run test-nginx --imagenginx --restartNever kubectl expose pod test-nginx --port80 kubectl run test-curl --imagecurlimages/curl --restartNever --rm -it -- sh curl test-nginx注意如果使用Minikube等本地环境建议分配至少4CPU和8GB内存。我曾在一台2CPU的机器上部署时reviews服务的Java进程频繁OOM。2.2 命名空间规划建议为Bookinfo创建独立命名空间# bookinfo-ns.yaml apiVersion: v1 kind: Namespace metadata: name: bookinfo labels: istio-injection: enabled # 如需集成Istio需添加此标签应用这个配置后所有后续资源都应指定namespace: bookinfo。不推荐使用default命名空间这会导致后期难以区分管理边界。3. 核心服务YAML配置详解3.1 Productpage服务部署作为前端入口productpage的配置最具代表性# productpage-deployment.yaml apiVersion: apps/v1 kind: Deployment metadata: name: productpage-v1 namespace: bookinfo spec: replicas: 2 selector: matchLabels: app: productpage version: v1 template: metadata: labels: app: productpage version: v1 spec: containers: - name: productpage image: docker.io/istio/examples-bookinfo-productpage-v1:1.16.2 imagePullPolicy: IfNotPresent ports: - containerPort: 9080 env: - name: LOG_LEVEL value: debug resources: requests: cpu: 100m memory: 128Mi limits: cpu: 200m memory: 256Mi livenessProbe: httpGet: path: /health port: 9080 initialDelaySeconds: 30 periodSeconds: 5 readinessProbe: httpGet: path: /health port: 9080 initialDelaySeconds: 20 periodSeconds: 5关键配置解析镜像版本固定为1.16.2最新稳定版避免使用latest标签资源限制根据实际压力测试调整初期可设置较低值健康检查路径/health是应用内置端点环境变量LOG_LEVEL控制日志详细程度3.2 Details服务配置details服务相对简单但需要注意# details-deployment.yaml apiVersion: apps/v1 kind: Deployment metadata: name: details-v1 namespace: bookinfo spec: replicas: 1 selector: matchLabels: app: details version: v1 template: metadata: labels: app: details version: v1 spec: containers: - name: details image: docker.io/istio/examples-bookinfo-details-v1:1.16.2 imagePullPolicy: IfNotPresent ports: - containerPort: 9080 securityContext: runAsUser: 1000 # 非root用户运行 readOnlyRootFilesystem: true安全实践使用非root用户UID 1000只读根文件系统增强安全性单副本足够应对演示场景3.3 Reviews服务的多版本部署reviews服务有三个版本v1/v2/v3演示如何管理同一应用的不同变体# reviews-deployment.yaml apiVersion: apps/v1 kind: Deployment metadata: name: reviews-v1 namespace: bookinfo spec: replicas: 1 selector: matchLabels: app: reviews version: v1 template: metadata: labels: app: reviews version: v1 spec: containers: - name: reviews image: docker.io/istio/examples-bookinfo-reviews-v1:1.16.2 # ...类似配置省略... --- apiVersion: apps/v1 kind: Deployment metadata: name: reviews-v2 namespace: bookinfo spec: replicas: 1 selector: matchLabels: app: reviews version: v2 template: metadata: labels: app: reviews version: v2 spec: containers: - name: reviews image: docker.io/istio/examples-bookinfo-reviews-v2:1.16.2 env: - name: ENABLE_RATINGS value: true --- apiVersion: apps/v1 kind: Deployment metadata: name: reviews-v3 namespace: bookinfo spec: replicas: 1 selector: matchLabels: app: reviews version: v3 template: metadata: labels: app: reviews version: v3 spec: containers: - name: reviews image: docker.io/istio/examples-bookinfo-reviews-v3:1.16.2 env: - name: ENABLE_RATINGS value: true版本差异说明v1基础版本不调用ratings服务v2调用ratings并显示黑色星标v3调用ratings并显示红色星标3.4 Ratings服务配置ratings服务使用MySQL数据库需要额外配置# ratings-deployment.yaml apiVersion: apps/v1 kind: Deployment metadata: name: ratings-v1 namespace: bookinfo spec: replicas: 1 selector: matchLabels: app: ratings version: v1 template: metadata: labels: app: ratings version: v1 spec: containers: - name: ratings image: docker.io/istio/examples-bookinfo-ratings-v1:1.16.2 imagePullPolicy: IfNotPresent ports: - containerPort: 9080 env: - name: DB_TYPE value: mysql - name: MYSQL_DB_HOST value: mysql - name: MYSQL_DB_PORT value: 3306 - name: MYSQL_DB_USER value: root - name: MYSQL_DB_PASSWORD valueFrom: secretKeyRef: name: mysql-secret key: password配套的MySQL部署# mysql-deployment.yaml apiVersion: apps/v1 kind: Deployment metadata: name: mysql namespace: bookinfo spec: replicas: 1 selector: matchLabels: app: mysql template: metadata: labels: app: mysql spec: containers: - name: mysql image: mysql:5.7 env: - name: MYSQL_ROOT_PASSWORD valueFrom: secretKeyRef: name: mysql-secret key: password ports: - containerPort: 3306 volumeMounts: - name: mysql-persistent-storage mountPath: /var/lib/mysql volumes: - name: mysql-persistent-storage persistentVolumeClaim: claimName: mysql-pv-claim --- apiVersion: v1 kind: PersistentVolumeClaim metadata: name: mysql-pv-claim namespace: bookinfo spec: accessModes: - ReadWriteOnce resources: requests: storage: 1Gi密码应通过Secret管理kubectl create secret generic mysql-secret \ --namespacebookinfo \ --from-literalpasswordYourStrongPassword123!4. 服务暴露与网络配置4.1 创建Kubernetes Service每个Deployment需要对应的Service# bookinfo-services.yaml apiVersion: v1 kind: Service metadata: name: productpage namespace: bookinfo spec: ports: - port: 9080 name: http selector: app: productpage --- apiVersion: v1 kind: Service metadata: name: details namespace: bookinfo spec: ports: - port: 9080 name: http selector: app: details # ...其他Service类似配置...4.2 入口网关配置可选如需从集群外部访问需配置Ingress或LoadBalancer# bookinfo-gateway.yaml apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: bookinfo-ingress namespace: bookinfo annotations: nginx.ingress.kubernetes.io/rewrite-target: / spec: rules: - host: bookinfo.example.com http: paths: - path: / pathType: Prefix backend: service: name: productpage port: number: 9080如果使用Istio则需要配置VirtualService和GatewayapiVersion: networking.istio.io/v1alpha3 kind: Gateway metadata: name: bookinfo-gateway namespace: bookinfo spec: selector: istio: ingressgateway servers: - port: number: 80 name: http protocol: HTTP hosts: - * --- apiVersion: networking.istio.io/v1alpha3 kind: VirtualService metadata: name: bookinfo namespace: bookinfo spec: hosts: - * gateways: - bookinfo-gateway http: - match: - uri: exact: /productpage - uri: prefix: /static - uri: exact: /login - uri: exact: /logout - uri: prefix: /api/v1/products route: - destination: host: productpage port: number: 90805. 部署验证与问题排查5.1 基础检查流程# 查看所有资源状态 kubectl get all -n bookinfo # 检查Pod日志 kubectl logs -n bookinfo pod-name -c container-name # 进入容器调试 kubectl exec -it -n bookinfo pod-name -c container-name -- sh # 临时端口转发 kubectl port-forward -n bookinfo svc/productpage 9080:90805.2 常见问题解决方案问题1Pod处于CrashLoopBackOff状态检查日志获取崩溃原因确认资源配额是否足够验证配置文件语法是否正确问题2服务间调用失败使用busybox镜像测试DNS解析检查Service的selector标签是否匹配Pod验证网络策略是否阻止通信问题3MySQL连接失败确认Secret是否正确挂载检查MySQL日志验证初始化是否成功测试从其他Pod连接MySQL服务问题4Ingress无法访问确认Ingress Controller正常运行检查hosts文件或DNS解析验证Ingress注解是否支持使用的Controller6. 高级配置与优化建议6.1 资源配额管理为命名空间设置ResourceQuotaapiVersion: v1 kind: ResourceQuota metadata: name: bookinfo-quota namespace: bookinfo spec: hard: requests.cpu: 2 requests.memory: 4Gi limits.cpu: 4 limits.memory: 8Gi pods: 106.2 自动扩缩容配置为productpage配置HPAapiVersion: autoscaling/v2 kind: HorizontalPodAutoscaler metadata: name: productpage-hpa namespace: bookinfo spec: scaleTargetRef: apiVersion: apps/v1 kind: Deployment name: productpage-v1 minReplicas: 2 maxReplicas: 5 metrics: - type: Resource resource: name: cpu target: type: Utilization averageUtilization: 506.3 使用ConfigMap管理配置将环境变量移入ConfigMapapiVersion: v1 kind: ConfigMap metadata: name: bookinfo-config namespace: bookinfo data: LOG_LEVEL: debug ENABLE_RATINGS: true DB_TYPE: mysql然后在Deployment中引用envFrom: - configMapRef: name: bookinfo-config6.4 网络策略限制只允许必要通信apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: bookinfo-policy namespace: bookinfo spec: podSelector: {} policyTypes: - Ingress - Egress ingress: - from: - podSelector: matchLabels: app: productpage ports: - protocol: TCP port: 9080 egress: - to: - podSelector: matchLabels: app: details ports: - protocol: TCP port: 90807. 实际部署中的经验教训镜像版本管理虽然使用latest标签方便但在生产环境一定要固定版本。有次latest镜像更新导致兼容性问题花了半天时间排查。资源限制设置初期不给Java服务reviews设置内存限制结果它占用了整个节点资源。建议从128Mi开始逐步调整。健康检查配置readinessProbe的initialDelaySeconds太短会导致Pod永远无法就绪。曾经设置为5秒而应用启动需要15秒造成持续重启。标签标准化除了app和version标签建议添加team、tier等业务标签方便后期管理。我们曾因标签混乱导致无法批量操作。数据库连接池ratings服务连接MySQL时默认连接池大小可能不够需要根据压力测试调整。遇到过因连接池耗尽导致的503错误。本地开发技巧在minikube中可以通过以下命令快速重建所有组件kubectl delete ns bookinfo kubectl apply -f .