Docker Compose 到 Kubernetes 的迁移指南

概览与核心价值从 Docker Compose 迁移到 Kubernetes/Helm 能获得更强的编排能力、滚动升级与弹性伸缩。本文提供逐步迁移方法与参数验证，确保低风险上线。迁移映射关系`services` → `Deployment`/`StatefulSet``ports` → `Service``volumes` → `PersistentVolumeClaim` + `StorageClass``env` → `ConfigMap` / `Secret`示例：Compose 到 DeploymentCompose 片段：services:

web:

image: myapp:1.0.0

ports:

- "8080:8080"

environment:

- LOG_LEVEL=info

volumes:

- data:/var/lib/app

volumes:

data:

Kubernetes 清单：apiVersion: v1

kind: ConfigMap

metadata:

name: app-config

data:

LOG_LEVEL: "info"

---

apiVersion: apps/v1

kind: Deployment

metadata:

name: web

spec:

replicas: 3

selector:

matchLabels:

app: web

template:

metadata:

labels:

app: web

spec:

containers:

- name: web

image: myapp:1.0.0

ports:

- containerPort: 8080

envFrom:

- configMapRef:

name: app-config

volumeMounts:

- name: data

mountPath: /var/lib/app

volumes:

- name: data

persistentVolumeClaim:

claimName: app-data

---

apiVersion: v1

kind: PersistentVolumeClaim

metadata:

name: app-data

spec:

accessModes: ["ReadWriteOnce"]

resources:

requests:

storage: 10Gi

---

apiVersion: v1

kind: Service

metadata:

name: web

spec:

type: ClusterIP

selector:

app: web

ports:

- port: 8080

targetPort: 8080

Helm 化与发布策略使用 `values.yaml` 管理镜像、副本与资源开启 `rollingUpdate`，设置 `maxUnavailable` 与 `maxSurge`示例 `values.yaml` 关键字段：image:

repository: myapp

tag: 1.0.0

replicaCount: 3

resources:

requests:

cpu: 200m

memory: 256Mi

limits:

cpu: 500m

memory: 512Mi

参数与验证环境：`Kubernetes v1.28`、`Helm v3.13`。验证点：发布无中断：滚动升级期间可用性 99.9%（P95 时延变化 < 5%）配置映射：通过 `ConfigMap`/`Secret` 注入，变更可控存储：PVC 持久化数据，副本重建后数据不丢失最佳实践优先使用 `Deployment` 管理无状态服务，状态服务选择 `StatefulSet`将 Compose 环境变量迁移到 `ConfigMap/Secret`，统一配置使用 `Helm` 进行参数化，接入 CI/CD 实现自动化发布结论本文给出了从 Compose 到 Kubernetes 的映射、示例与验证步骤。按上述路径迁移可显著提升编排能力与发布的稳定性。