# more

## Active Active
流量都會進去

Internal node to node
- change the `gateway` helm chart/template,delte Chart&value? (or Replica=0)
--> maybe faster than `deploy the actual ap`
WAY
- deploy the actual ap(api provider) to two clusters(different network zone)
--> potential risk about data

Refer to API Comsumer code:
https://chatgpt.com/share/289ec517-82a5-44e6-8721-2481aa89b6b0

## Active Standby
network zone failover

# hand writing

# kubernetes Service Account

1. Role Binding (view|admin) @GITOPS-xxxxRepo
- service account list configuration
- service account **declare**
- service account namespace
- Merge into release branch for sync config. to k8s
- Check the Argo Live manifest
2. API Gateway set API Provider - granted_role(Service Account) @GITOPS-xxxxRepo
- Sync the api provider setting
3. Deployment.yaml @Collab. Frontend Server
- Helm chart
- value.yaml
- Collab. Operator SLB(http) or **API Endpoint** setting change
- Collab. Operator **Deploy** Frontend Server
4. Functional Testing `對整合Collab.進APIGW這項POC Task`
- 拉斐爾使用GUI
- PY Check APIGW Log for 確認流量進來
- 進而知道API使用情況
- 進而保護API Provider勉於DDoS