K8S Cluster DR Test and Verify¶

1. DR cluster prepare¶

Primary Cluster: sat-trs-01

DR Cluster: sat-trs-02

• 1.1 Check cluster sat-trs-01 resource and sat-trs-02 free resource, make sure DR cluster (sat-trs-02) have enough resource

• login primary cluster master node, and check namespace resource

kubectl get resourcequotas -n wimes-f130

If there are multiple namespaces, please count and sum them separately

• 1.2 Shutdown cluster sat-trs-01 all node. (Simulation cluster is not available)

• 1.3 User check sat-trs-01 application status. (Is it accessible?)

2. Migration application¶

Migration apps from sat-trs-01 to sat-trs-02

• 2.1 Login gitlab, and create new namespace @sat-trs-02

• 2.2 Edit dr namespace with Web IDE

• 2.3 Copy all namespace from sat-trs-01 to sat-trs-02

• 2.4 Check dr namespace created @sat-trs-02

• 2.5 Check pod@namespace deploy status

3. Switch k8s FQDN mapping¶

• 3.1 Info network team change sat-trs-01 L4 IP mapping to sat-trs-02 worker node

After network team changed, use below script to check

curl -v bgd.wzs-sat-trs-01.wzsk8s.wistron.com

• 3.2 Check application status

• 3.3 Confirm again the k8s node used by the application