Migrate k8s runtime off h2 profile and raise replica floor for centralized DB

[Copilot]

This change aligns the Kubernetes/GCP workload with a centralized database setup by removing implicit h2 runtime behavior and increasing pod scaling limits. It updates both container startup profile selection and deployment autoscaling bounds to support multi-replica operation.

• Runtime profile selection (container startup)

  • Replaced hardcoded h2 startup profile in Dockerfile with environment-driven profile selection.
  • Added default fallback to default profile when SPRING_PROFILES_ACTIVE is not provided.

• Kubernetes profile wiring (GCP/local deploy manifest)

  • Added explicit SPRING_PROFILES_ACTIVE=default in kubernetes/deploy.yml container env to ensure non-h2 workload behavior on cluster deployments.

• Replica and HPA scaling update

  • Increased Deployment replicas from 1 to 2.
  • Increased HPA bounds from min=1/max=1 to min=2/max=4.

ENTRYPOINT [ "sh", "-c", "gradle bootRun --args=\"--spring.profiles.active=${SPRING_PROFILES_ACTIVE:-default}\"" ]

spec:
  replicas: 2
  template:
    spec:
      containers:
        - env:
            - name: SPRING_PROFILES_ACTIVE
              value: "default"
---
spec:
  minReplicas: 2
  maxReplicas: 4

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.