By mistake, I have the assumption that 7.6.2 is released on container and so I upgraded thee configurations and applied and ECK accepted the configuration.
Unfortunately the pods are failing to start and I can't rollback to 7.6.1.
Can anyone give me a workaround?
Hi @Ahmad_Al-Masry, that's an identified issue in our Github repository: https://github.com/elastic/cloud-on-k8s/issues/2455.
Until we figure out the best way to fix it, I think you can try the following:
- disable the validation webhook (
kubectl delete validatingwebhookconfiguration elastic-webhook.k8s.elastic.co)
- apply the manifest with the rollbacked version
- manually delete the Pod that is failing to start in the new unknown version (
kubectl delete pod <pod_name>)
Once everything is back to its normal state, you can re-create the validating webhoook by reapplying ECK yaml manifests (the one you applied to install ECK).
With https://github.com/elastic/cloud-on-k8s/issues/2455 we'll try to figure out a better way to do that.