Page Comparison

...

1. Bring Down Nginx-Ingress Controller

   • Scale down the nginx-ingress controller to zero replicas.

     Code Block
     language bash
     kubectl scale deployment nginx-ingress-controller --replicas=0 -n <namespace>

2. Monitor Kafka Lags

   • Monitor Kafka consumer lags until they reach zero to ensure no pending messages.

     Code Block
     language bash
     kafka-consumer-groups --bootstrap-server <kafka-broker> --describe --group <consumer-group>

     If latest monitoring is available, use Kafka-UI to monitor Kafka consumer lags.

     Code Block
     language bashnone
     kubectl port-forward svc/kafka-ui 8080:8080 -n <namespace> # visit http://localhost:8080/kafka-ui to access dashboard

3. Backup RDS DB Instance

   • Create a snapshot of the RDS instance from AWS console or using below AWS CLI cmd.

     Code Block
     language bash
     aws rds create-db-snapshot --region <region> --db-instance-identifier <db-instance-id> --db-snapshot-identifier <snapshot-id>

...

1. Login to DB and Execute basic SQL Queries

   • Login using existing credentials and run basic SQL queries.

   • Make sure both Admin & Read credentials are working as expected.

2. Restart Services

   • Restart all services connected to the database to ensure they are utilizing the updated instance.

3. Scale Up Nginx-Ingress Controller

   • Scale up the nginx-ingress controller to required N replicas.

     Code Block
     kubectl scale deployment nginx-ingress-controller --replicas=N -n <namespace>

4. Verify System Health

   • Monitor the overall system health to ensure everything is functioning as expected.

...