config:
  aws:region: us-west-2
  core:env: prod
  eks:publicAccessCidrs:
    # jump server instance
    - 35.80.240.167/32
    # from company network
    - 1.203.96.0/29
    - 117.134.13.184/29
    - 103.85.175.128/29
    - 211.95.24.8/29
    - 101.207.139.187/32
    - 183.129.144.200/29
    - 39.170.92.156/32
    - 183.6.107.178/32
    - 119.136.31.176/32
    - 117.50.84.111/32
    - 120.92.122.221/32
    - 120.92.20.132/32
    - 106.75.116.22/32
    - 118.194.230.143/32
    - 120.92.100.187/32
    - 152.104.28.129/32
    - 120.92.102.252/32
    - 63.70.2.110/32
    - 104.250.50.243/32
    - 106.75.52.157/32
    - 152.32.204.171/32
    - 120.92.55.209/32
    - 120.92.55.116/32
    - 120.92.72.28/32
    - 104.250.50.40/32
    - 20.63.218.57/32
    - 45.64.247.96/27
    - 173.248.249.128/27
    - 203.90.236.192/27
    - 128.1.49.85/32
    - 117.50.66.239/32
    - 40.74.68.232/32
    - 58.94.102.181/32
    - 118.194.230.143/32
    # github action runner
    - 35.233.250.206/32
    - 104.196.246.224/32
    # ArgoCD
    - 34.69.36.199/32
  eks:adminRoleARNs:
    - arn:aws:iam::557537366020:role/argocd-oidc-role
    - arn:aws:iam::557537366020:role/clinic-cicd
    - arn:aws:iam::557537366020:role/clinic-eks # used to access cluster in local
    - arn:aws:iam::557537366020: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: 2
      minSize: 0
      maxSize: 2
      labels:
        node_type: admin
    - name: jumppod
      instanceType: m5.xlarge
      subnetIDs: [] # use private subnets by default
      desiredCapacity: 2
      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: prod-devops2base
      serviceName: "com.amazonaws.vpce.us-west-2.vpce-svc-0bb4e079eb3f71c7b" # "devops2base-prod-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-08c1f88c09c868cb6"] # only support usw2-az1
      sgIngressProtocol: tcp
      sgIngressFromPort: 4000
      sgIngressToPort: 4000
      privateDnsEnabled: true
    - name: prod-eventbus-b1
      serviceName: "com.amazonaws.vpce.us-west-2.vpce-svc-049e44ec09186bbca" # "ES-tidbcloud-eventbus-prod-b1" in base account
      subnetIDs: ["subnet-04da98be809ab2b60"] # only support usw2-az3
      sgIngressProtocol: tcp
      sgIngressFromPort: 9092
      sgIngressToPort: 9092
    - name: prod-eventbus-b2
      serviceName: "com.amazonaws.vpce.us-west-2.vpce-svc-07f3b12bc6857ac09" # "ES-tidbcloud-eventbus-prod-b2" in base account
      subnetIDs: ["subnet-08c1f88c09c868cb6"] # only support usw2-az1
      sgIngressProtocol: tcp
      sgIngressFromPort: 9092
      sgIngressToPort: 9092
    - name: prod-eventbus-b3
      serviceName: "com.amazonaws.vpce.us-west-2.vpce-svc-0c7fb8a60c271c8e4" # "ES-tidbcloud-eventbus-prod-b3" in base account
      subnetIDs: ["subnet-0ed936771d5c00fab"] # 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:CSAxR8cewbA=:v1:AjzmL2qFxBQkqKEr:UBOKVleskt/iYxMo+ODNkw9eng3IFg==