# skaffold.yaml
apiVersion: skaffold/v4beta7
kind: Config
metadata:
  name: nomulus-skaffold
profiles:
- name: crash
  # Note: The stable profile intentionally includes partial-phase-5 manifests alongside
  # primary workloads. This ensures that the candidate image is deployed across both deployments,
  # maintaining stable pod and GKE node allocation to prevent churn on nodes hosting persistent
  # registrar sessions.
  manifests:
    rawYaml:
    - ../../jetty/kubernetes/nomulus-crash-backend.yaml
    - ../../jetty/kubernetes/nomulus-crash-console.yaml
    - ../../jetty/kubernetes/nomulus-crash-frontend.yaml
    - ../../jetty/kubernetes/nomulus-crash-pubapi.yaml
    - ../../jetty/kubernetes/nomulus-crash-epp-server.yaml
    - ../../jetty/kubernetes/nomulus-crash-backend-partial-phase-5.yaml
    - ../../jetty/kubernetes/nomulus-crash-console-partial-phase-5.yaml
    - ../../jetty/kubernetes/nomulus-crash-frontend-partial-phase-5.yaml
    - ../../jetty/kubernetes/nomulus-crash-pubapi-partial-phase-5.yaml
    - ../../jetty/kubernetes/nomulus-crash-epp-server-partial-phase-5.yaml
  deploy:
    kubectl: { }
- name: crash-partial-phase-1
  manifests:
    rawYaml:
    - ../../jetty/kubernetes/nomulus-crash-backend-partial-phase-1.yaml
    - ../../jetty/kubernetes/nomulus-crash-console-partial-phase-1.yaml
    - ../../jetty/kubernetes/nomulus-crash-frontend-partial-phase-1.yaml
    - ../../jetty/kubernetes/nomulus-crash-pubapi-partial-phase-1.yaml
    - ../../jetty/kubernetes/nomulus-crash-epp-server-partial-phase-1.yaml
  deploy:
    kubectl: { }
- name: crash-partial-phase-5
  manifests:
    rawYaml:
    - ../../jetty/kubernetes/nomulus-crash-backend-partial-phase-5.yaml
    - ../../jetty/kubernetes/nomulus-crash-console-partial-phase-5.yaml
    - ../../jetty/kubernetes/nomulus-crash-frontend-partial-phase-5.yaml
    - ../../jetty/kubernetes/nomulus-crash-pubapi-partial-phase-5.yaml
    - ../../jetty/kubernetes/nomulus-crash-epp-server-partial-phase-5.yaml
  deploy:
    kubectl: { }
- name: sandbox
  # Note: The stable profile intentionally includes partial-phase-5 manifests alongside
  # primary workloads. This ensures that the candidate image is deployed across both deployments,
  # maintaining stable pod and GKE node allocation to prevent churn on nodes hosting persistent
  # registrar sessions.
  manifests:
    rawYaml:
    - ../../jetty/kubernetes/nomulus-sandbox-backend.yaml
    - ../../jetty/kubernetes/nomulus-sandbox-console.yaml
    - ../../jetty/kubernetes/nomulus-sandbox-frontend.yaml
    - ../../jetty/kubernetes/nomulus-sandbox-pubapi.yaml
    - ../../jetty/kubernetes/nomulus-sandbox-epp-server.yaml
    - ../../jetty/kubernetes/nomulus-sandbox-backend-partial-phase-5.yaml
    - ../../jetty/kubernetes/nomulus-sandbox-console-partial-phase-5.yaml
    - ../../jetty/kubernetes/nomulus-sandbox-frontend-partial-phase-5.yaml
    - ../../jetty/kubernetes/nomulus-sandbox-pubapi-partial-phase-5.yaml
    - ../../jetty/kubernetes/nomulus-sandbox-epp-server-partial-phase-5.yaml
  deploy:
    kubectl: { }
- name: sandbox-partial-phase-1
  manifests:
    rawYaml:
    - ../../jetty/kubernetes/nomulus-sandbox-backend-partial-phase-1.yaml
    - ../../jetty/kubernetes/nomulus-sandbox-console-partial-phase-1.yaml
    - ../../jetty/kubernetes/nomulus-sandbox-frontend-partial-phase-1.yaml
    - ../../jetty/kubernetes/nomulus-sandbox-pubapi-partial-phase-1.yaml
    - ../../jetty/kubernetes/nomulus-sandbox-epp-server-partial-phase-1.yaml
  deploy:
    kubectl: { }
- name: sandbox-partial-phase-5
  manifests:
    rawYaml:
    - ../../jetty/kubernetes/nomulus-sandbox-backend-partial-phase-5.yaml
    - ../../jetty/kubernetes/nomulus-sandbox-console-partial-phase-5.yaml
    - ../../jetty/kubernetes/nomulus-sandbox-frontend-partial-phase-5.yaml
    - ../../jetty/kubernetes/nomulus-sandbox-pubapi-partial-phase-5.yaml
    - ../../jetty/kubernetes/nomulus-sandbox-epp-server-partial-phase-5.yaml
  deploy:
    kubectl: { }
- name: production
  # Note: The stable profile intentionally includes partial-phase-5 manifests alongside
  # primary workloads. This ensures that the candidate image is deployed across both deployments,
  # maintaining stable pod and GKE node allocation to prevent churn on nodes hosting persistent
  # registrar sessions.
  manifests:
    rawYaml:
    - ../../jetty/kubernetes/nomulus-production-backend.yaml
    - ../../jetty/kubernetes/nomulus-production-console.yaml
    - ../../jetty/kubernetes/nomulus-production-frontend.yaml
    - ../../jetty/kubernetes/nomulus-production-pubapi.yaml
    - ../../jetty/kubernetes/nomulus-production-epp-server.yaml
    - ../../jetty/kubernetes/nomulus-production-backend-partial-phase-5.yaml
    - ../../jetty/kubernetes/nomulus-production-console-partial-phase-5.yaml
    - ../../jetty/kubernetes/nomulus-production-frontend-partial-phase-5.yaml
    - ../../jetty/kubernetes/nomulus-production-pubapi-partial-phase-5.yaml
    - ../../jetty/kubernetes/nomulus-production-epp-server-partial-phase-5.yaml
  deploy:
    kubectl: { }
- name: production-partial-phase-1
  manifests:
    rawYaml:
    - ../../jetty/kubernetes/nomulus-production-backend-partial-phase-1.yaml
    - ../../jetty/kubernetes/nomulus-production-console-partial-phase-1.yaml
    - ../../jetty/kubernetes/nomulus-production-frontend-partial-phase-1.yaml
    - ../../jetty/kubernetes/nomulus-production-pubapi-partial-phase-1.yaml
    - ../../jetty/kubernetes/nomulus-production-epp-server-partial-phase-1.yaml
  deploy:
    kubectl: { }
- name: production-partial-phase-5
  manifests:
    rawYaml:
    - ../../jetty/kubernetes/nomulus-production-backend-partial-phase-5.yaml
    - ../../jetty/kubernetes/nomulus-production-console-partial-phase-5.yaml
    - ../../jetty/kubernetes/nomulus-production-frontend-partial-phase-5.yaml
    - ../../jetty/kubernetes/nomulus-production-pubapi-partial-phase-5.yaml
    - ../../jetty/kubernetes/nomulus-production-epp-server-partial-phase-5.yaml
  deploy:
    kubectl: { }