Edit: if you are experiencing a similar issue please refer to If you upgraded Elasticsearch to the wrong version first.
Hi @Ahmad_Al-Masry, that's an identified issue in our Github repository: Versions existence should be validated · Issue #2455 · elastic/cloud-on-k8s · GitHub.
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 Versions existence should be validated · Issue #2455 · elastic/cloud-on-k8s · GitHub we'll try to figure out a better way to do that.