当前位置：首页 > news >正文

云原生应用的多环境部署策略

news 2026/6/15 19:55:46

云原生应用的多环境部署策略

🔥 硬核开场

各位技术老铁，今天咱们聊聊云原生应用的多环境部署策略。别跟我扯那些理论，直接上干货！在云原生时代，应用的部署环境越来越复杂，从开发、测试到生产，每个环境都有不同的配置和要求。不搞多环境部署策略？那你的应用可能在生产环境中频繁踩坑，让你叫苦不迭。

📋 核心概念

多环境部署是什么？

多环境部署是指在不同的环境中部署相同的应用，但使用不同的配置和资源。常见的环境包括开发环境、测试环境、预生产环境和生产环境。

多环境部署的核心原则

环境隔离：不同环境之间应该相互隔离，避免相互影响
配置管理：使用配置管理工具，管理不同环境的配置
自动化部署：通过CI/CD流水线，实现自动化部署
一致性：确保不同环境的部署流程和配置保持一致
可回滚：支持快速回滚到之前的版本

🚀 实践指南

1. 环境管理

命名空间配置

apiVersion: v1 kind: Namespace metadata: name: dev --- apiVersion: v1 kind: Namespace metadata: name: test --- apiVersion: v1 kind: Namespace metadata: name: staging --- apiVersion: v1 kind: Namespace metadata: name: prod

资源配额配置

apiVersion: v1 kind: ResourceQuota metadata: name: dev-quota namespace: dev spec: hard: requests.cpu: "4" requests.memory: "8Gi" limits.cpu: "8" limits.memory: "16Gi" pods: "20" services: "10" --- apiVersion: v1 kind: ResourceQuota metadata: name: prod-quota namespace: prod spec: hard: requests.cpu: "16" requests.memory: "32Gi" limits.cpu: "32" limits.memory: "64Gi" pods: "50" services: "20"

2. 配置管理

ConfigMap配置

# 开发环境配置 apiVersion: v1 kind: ConfigMap metadata: name: app-config namespace: dev data: APP_ENV: "development" DB_HOST: "dev-db" DB_PORT: "5432" DB_NAME: "dev_db" LOG_LEVEL: "debug" --- # 生产环境配置 apiVersion: v1 kind: ConfigMap metadata: name: app-config namespace: prod data: APP_ENV: "production" DB_HOST: "prod-db" DB_PORT: "5432" DB_NAME: "prod_db" LOG_LEVEL: "info"

Secret配置

# 开发环境密钥 apiVersion: v1 kind: Secret metadata: name: app-secrets namespace: dev type: Opaque data: DB_USER: <base64-encoded-dev-user> DB_PASSWORD: <base64-encoded-dev-password> API_KEY: <base64-encoded-dev-api-key> --- # 生产环境密钥 apiVersion: v1 kind: Secret metadata: name: app-secrets namespace: prod type: Opaque data: DB_USER: <base64-encoded-prod-user> DB_PASSWORD: <base64-encoded-prod-password> API_KEY: <base64-encoded-prod-api-key>

3. CI/CD流水线

GitHub Actions配置

name: Multi-Environment Deployment on: push: branches: - main pull_request: branches: - main jobs: build: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - name: Set up Node.js uses: actions/setup-node@v2 with: node-version: '14' - name: Install dependencies run: npm install - name: Build run: npm run build - name: Test run: npm test - name: Build and push Docker image uses: docker/build-push-action@v2 with: context: . push: true tags: ${{ secrets.DOCKER_USERNAME }}/app:${{ github.sha }} deploy-dev: needs: build runs-on: ubuntu-latest if: github.ref == 'refs/heads/main' steps: - uses: actions/checkout@v2 - name: Set up kubectl uses: azure/setup-kubectl@v1 with: version: 'v1.21.0' - name: Configure kubeconfig run: | mkdir -p ~/.kube echo "${{ secrets.KUBE_CONFIG_DEV }}" > ~/.kube/config - name: Deploy to Dev run: kubectl apply -f kubernetes/dev/ deploy-test: needs: deploy-dev runs-on: ubuntu-latest if: github.ref == 'refs/heads/main' steps: - uses: actions/checkout@v2 - name: Set up kubectl uses: azure/setup-kubectl@v1 with: version: 'v1.21.0' - name: Configure kubeconfig run: | mkdir -p ~/.kube echo "${{ secrets.KUBE_CONFIG_TEST }}" > ~/.kube/config - name: Deploy to Test run: kubectl apply -f kubernetes/test/ deploy-prod: needs: deploy-test runs-on: ubuntu-latest if: github.ref == 'refs/heads/main' steps: - uses: actions/checkout@v2 - name: Set up kubectl uses: azure/setup-kubectl@v1 with: version: 'v1.21.0' - name: Configure kubeconfig run: | mkdir -p ~/.kube echo "${{ secrets.KUBE_CONFIG_PROD }}" > ~/.kube/config - name: Deploy to Prod run: kubectl apply -f kubernetes/prod/

4. 部署策略

开发环境部署

apiVersion: apps/v1 kind: Deployment metadata: name: app namespace: dev spec: replicas: 2 selector: matchLabels: app: app template: metadata: labels: app: app spec: containers: - name: app image: your-registry/app:latest resources: requests: memory: "256Mi" cpu: "200m" limits: memory: "512Mi" cpu: "500m" envFrom: - configMapRef: name: app-config - secretRef: name: app-secrets ports: - containerPort: 8080

生产环境部署

apiVersion: apps/v1 kind: Deployment metadata: name: app namespace: prod spec: replicas: 6 strategy: type: RollingUpdate rollingUpdate: maxSurge: 25% maxUnavailable: 25% selector: matchLabels: app: app template: metadata: labels: app: app spec: containers: - name: app image: your-registry/app:latest resources: requests: memory: "512Mi" cpu: "500m" limits: memory: "1Gi" cpu: "1" envFrom: - configMapRef: name: app-config - secretRef: name: app-secrets ports: - containerPort: 8080 livenessProbe: httpGet: path: /health port: 8080 initialDelaySeconds: 30 periodSeconds: 10 readinessProbe: httpGet: path: /ready port: 8080 initialDelaySeconds: 15 periodSeconds: 5

5. 网络配置

开发环境服务

apiVersion: v1 kind: Service metadata: name: app namespace: dev spec: selector: app: app ports: - port: 80 targetPort: 8080 type: ClusterIP

生产环境服务

apiVersion: v1 kind: Service metadata: name: app namespace: prod spec: selector: app: app ports: - port: 80 targetPort: 8080 type: ClusterIP --- apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: app-ingress namespace: prod annotations: kubernetes.io/ingress.class: "nginx" cert-manager.io/cluster-issuer: "letsencrypt-prod" spec: tls: - hosts: - app.example.com secretName: app-tls rules: - host: app.example.com http: paths: - path: / pathType: Prefix backend: service: name: app port: number: 80