633d0a9a76
The recent upversion of the nginx app (https://review.opendev.org/c/starlingx/nginx-ingress-controller-armada-app/+/782326) enabled the nginx admissionWebhook and this introduced an issue in the restore procedure. The proposed solution is to use the lifecycle operator to delete the nginx admissionWebhook before the backup. If we do this, the backup of the etcd database will not have the nginx webhook and the restore will succeed. Note that the solution implies a deletion of a resource in the nginx app. Because of this, there are some procedural changes to the backup and restore that the user must do: - After backup completes the following steps must be done: 1. $ system helm-override-update nginx-ingress-controller ingress-nginx kube-system --set controller.admissionWebhooks.enabled=true 2. reapply the nginx app to restore the admissionWebhook: $ system application-apply nginx-ingress-controller - After the whole restore procedure (i.e after all the nodes are restored and unlocked, apps are in applied state and 'system restore-complete' was executed) the user must do the same steps as above to restore the nginx webhook: 1. $ system helm-override-update nginx-ingress-controller ingress-nginx kube-system --set controller.admissionWebhooks.enabled=true 2. $ system application-apply nginx-ingress-controller Depends-On: I61156db05970aa03c96ddc8533fdd4f4a680b334 Depends-On: I0ebab45f4846cbcd25fecac6bf99195d9047eb8a Depends-On: I648e940f8104307e111213afd511f8fca19e39ab Closes-Bug: 1923185 Signed-off-by: Mihnea Saracin <Mihnea.Saracin@windriver.com> Change-Id: I9ca56329cfa353e7938a9fd8e94c50295c6a0778
2 lines
72 B
Plaintext
2 lines
72 B
Plaintext
stx-nginx-ingress-controller-helm
|
|
python-k8sapp-nginx-ingress-controller |