config:
  aws:region: us-west-2
  core:env: staging
  eks:publicAccessCidrs:
    - 0.0.0.0/0
  eks:adminRoleARNs:
    - arn:aws:iam::552185537300:role/argocd-oidc-role
    - arn:aws:iam::552185537300:role/clinic-ci
    - arn:aws:iam::552185537300:role/autonomous-cent-stor-dev # used to access cluster in local
    - arn:aws:iam::552185537300:role/jump-service-role # used by jump service to access cluster
  eks:addons: # extra addons to install
    - name: aws-ebs-csi-driver
  eks:nodeGroups:
    - name: admin
      instanceType: m5.xlarge
      subnetIDs: [] # use private subnets by default
      desiredCapacity: 0
      minSize: 0
      maxSize: 2
      labels:
        node_type: admin
    - name: jumppod-large
      instanceType: m5.xlarge
      subnetIDs: [] # use private subnets by default
      desiredCapacity: 1
      minSize: 0
      maxSize: 2
      labels:
        node_type: jumppod
      taints:
        - key: dedicated
          value: jumppod
          effect: NO_SCHEDULE
  privatelink:privatelinks:
    - name: devops2db
      serviceName: "com.amazonaws.vpce.us-west-2.vpce-svc-0679cde159cc189f2" # "devops-to-dw-endpoint-service" in escalation-dev account
      sgIngressProtocol: tcp
      sgIngressFromPort: 4000
      sgIngressToPort: 4000
    - name: dev-devops2base
      serviceName: "com.amazonaws.vpce.us-west-2.vpce-svc-090ba904327cbbba1" # "devops2base-dev-ep" in base account
    - name: staging-devops2base
      serviceName: "com.amazonaws.vpce.us-west-2.vpce-svc-0d206c48d2c9ac54e" # "devops2base-staging-ep" in base account
    - name: aiops-db
      serviceName: "com.amazonaws.vpce.us-west-2.vpce-svc-0bb63f101e9c97f54" # endpoint service of serverless db in tidbcloud
      subnetIDs: ["subnet-0d659f804ef1a1749"] # only support usw2-az1
      sgIngressProtocol: tcp
      sgIngressFromPort: 4000
      sgIngressToPort: 4000
      privateDnsEnabled: true
    - name: dev-eventbus-b1
      serviceName: "com.amazonaws.vpce.us-west-2.vpce-svc-05d8a30dc91147a6d" # "endpoint-tidbcloud-eventbus-dev-1-b1" in base account
      subnetIDs: ["subnet-0d659f804ef1a1749"] # only support usw2-az1
      sgIngressProtocol: tcp
      sgIngressFromPort: 9092
      sgIngressToPort: 9092
    - name: dev-eventbus-b2
      serviceName: "com.amazonaws.vpce.us-west-2.vpce-svc-0f69af2b5dcd7637d" # "endpoint-tidbcloud-eventbus-dev-1-b2" in base account
      subnetIDs: ["subnet-052a6c6e266178613"] # only support usw2-az2
      sgIngressProtocol: tcp
      sgIngressFromPort: 9092
      sgIngressToPort: 9092
    - name: staging-eventbus-b1
      serviceName: "com.amazonaws.vpce.us-west-2.vpce-svc-00c027a9d27fe1df0" # "endpoint-tidbcloud-eventbus-staging-b1" in base account
      subnetIDs: ["subnet-0d659f804ef1a1749"] # only support usw2-az1
      sgIngressProtocol: tcp
      sgIngressFromPort: 9092
      sgIngressToPort: 9092
    - name: staging-eventbus-b2
      serviceName: "com.amazonaws.vpce.us-west-2.vpce-svc-024e5c4a5ac0642c8" # "endpoint-tidbcloud-eventbus-staging-b2" in base account
      subnetIDs: ["subnet-052a6c6e266178613"] # only support usw2-az2
      sgIngressProtocol: tcp
      sgIngressFromPort: 9092
      sgIngressToPort: 9092
    - name: o11y-monitoring
      serviceName: "com.amazonaws.vpce.us-west-2.vpce-svc-0568d7d397b889632" # endpoint service in corrsponding o11y cluster
      sgIngressProtocol: tcp
      sgIngressFromPort: 80
      sgIngressToPort: 80
      privateDnsEnabled: true
encryptionsalt: v1:j/AA6OkuQ7Y=:v1:70DBJSBBiMYsILsB:7PDtUt+JeXhxu0BwuLfiALxYAGpXvg==