Force delete ic-nginx-ingress-controller during restore
During restore, etcd will be in a confused state. If multiple nodes
were configured during backup, pods assigned to those other nodes,
eg. controller-1, will only be removable with '--force' flag.
To preview this, run 'kubectl get pods --all-namespaces'.
This will show that pods are running on other nodes,
despite the nodes not being installed yet.
TEST PLAN
Backup & Restore on virtual AIO-DX (Debian)
Reviewed: https:/ /review. opendev. org/c/starlingx /ansible- playbooks/ +/855037 /opendev. org/starlingx/ ansible- playbooks/ commit/ 3a5a56cf82e0251 e6c34461de4d92a 9568552bc4
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 3a5a56cf82e0251 e6c34461de4d92a 9568552bc4
Author: Joshua Kraitberg <email address hidden>
Date: Mon Aug 29 10:00:09 2022 -0400
Force delete ic-nginx- ingress- controller during restore
During restore, etcd will be in a confused state. If multiple nodes
were configured during backup, pods assigned to those other nodes,
eg. controller-1, will only be removable with '--force' flag.
To preview this, run 'kubectl get pods --all-namespaces'.
This will show that pods are running on other nodes,
despite the nodes not being installed yet.
TEST PLAN
Backup & Restore on virtual AIO-DX (Debian)
Closes-Bug: 1988056 2c52ad69cda77d3 26fa19b7d12
Signed-off-by: Joshua Kraitberg <email address hidden>
Change-Id: Ibeb1592d83d461