Spring Cloud 生产部署：Docker + Kubernetes + GraalVM 原生镜像方案

2.2 Dockerfile（GraalVM 原生镜像）

# Stage 1: Build
FROM ghcr.io/graalvm/native-image-community:21 AS builder
WORKDIR /build
COPY . .
RUN --mount=type=cache,target=/root/.m2 mvn -B package -Pnative -DskipTests

# Stage 2: Runtime
FROM ubuntu:24.04
WORKDIR /app
COPY --from=builder /build/target/*.jar /app/app.jar
# 或 native executable
# COPY --from=builder /build/target/my-app /app/my-app
EXPOSE 8080
ENTRYPOINT ["/app/my-app"]
# 或 java -jar app.jar

• 构建：mvn spring-boot:build-image 或 docker build -t order-service:native .
• 优势：镜像大小 50-100MB，启动 <50ms

2.3 深度原理剖析（GraalVM）

• AOT 编译：Ahead-of-Time，预编译字节码为本地可执行文件
• 为什么快：无 JIT 热启动，静态链接，内存峰值低
• 坑：反射/动态代理需手动 hint（Spring AOT 自动生成大部分配置）

源码级：Spring Boot Native 插件生成 reflection 配置、resource hints

// 简化版 NativeHint
@NativeHint(types = {OrderController.class})
public class Hints {}

三、Kubernetes 部署实战

3.1 Deployment YAML（GraalVM 原生）

apiVersion: apps/v1
kind: Deployment
metadata:
  name: order-service
spec:
  replicas: 3
  selector:
    matchLabels:
      app: order-service
  template:
    metadata:
      labels:
        app: order-service
    spec:
      containers:
      - name: order-service
        image: your-repo/order-service:native
        ports:
        - containerPort: 8080
        resources:
          requests:
            cpu: "200m"
            memory: "256Mi"
          limits:
            cpu: "500m"
            memory: "512Mi"
        env:
        - name: SPRING_PROFILES_ACTIVE
          value: "prod"
        livenessProbe:
          httpGet:
            path: /actuator/health
            port: 8080
          initialDelaySeconds: 10
          periodSeconds: 5
        readinessProbe:
          httpGet:
            path: /actuator/health/readiness
            port: 8080
          initialDelaySeconds: 5
          periodSeconds: 3

3.2 Service + Ingress

apiVersion: v1
kind: Service
metadata:
  name: order-service
spec:
  selector:
    app: order-service
  ports:
  - protocol: TCP
    port: 80
    targetPort: 8080
  type: ClusterIP
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: order-ingress
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /
spec:
  rules:
  - host: api.example.com
    http:
      paths:
      - path: /order
        pathType: Prefix
        backend:
          service:
            name: order-service
            port:
              number: 80

3.3 HPA + ConfigMap/Secret

apiVersion: autoscaling/v2
kind: HorizontalPodAutoscaler
metadata:
  name: order-hpa
spec:
  scaleTargetRef:
    apiVersion: apps/v1
    kind: Deployment
    name: order-service
  minReplicas: 2
  maxReplicas: 10
  metrics:
  - type: Resource
    resource:
      name: cpu
      target:
        type: Utilization
        averageUtilization: 60
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: order-config
data:
  application.yml: |
    spring:
      cloud:
        nacos:
          discovery:
            server-addr: nacos:8848

• Secret 用于敏感配置（如 DB 密码）

3.4 深度原理剖析（K8s）

• Deployment：控制器管理 ReplicaSet + Pod
• HPA：Metrics Server 采集 CPU/Memory，自动扩缩
• Service：ClusterIP + DNS 解析
• Ingress：Nginx Ingress Controller 路由 + TLS

四、生产级应用：灰度发布 + 滚动更新 + 监控

4.1 灰度发布（Canary）

• 用 K8s Deployment + Service 流量权重（Istio/VirtualService）
• 示例：新版本镜像 tag:v2，Deployment replicas: 1，Service traffic split

4.2 滚动更新 + 零宕机

strategy:
  type: RollingUpdate
  rollingUpdate:
    maxSurge: 25%
    maxUnavailable: 0

4.3 集成 Nacos + SkyWalking

• Pod 环境变量注入 Nacos Server
• SkyWalking Agent Sidecar 注入，追踪全链路

五、生产避坑 & 优化

5.1 常见坑 & 解法

1. GraalVM 反射缺失 → 用 native-image-agent 生成 hints
2. Pod 启动慢 → Readiness Probe 调 initialDelaySeconds
3. 资源浪费 → Requests/Limits 精确设置 + VPA
4. 镜像太大 → 多阶段构建 + distroless base
5. 监控缺失 → Actuator + Prometheus + Grafana 必备

5.2 优化推荐

• GitOps：ArgoCD/Flux 管理 YAML
• ARM 支持：GraalVM Native + multi-arch Docker