You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However if a user made a mistake an upgrade to the wrong version or a downgrade is made necessary for other reasons (bug!) it is to be expected that all related resources have already been upgraded to the new version.
Currently this make the downgrade process hard because you have to scale down the operator or disable the validating webhook to force the downgrade on the non-Elasticsearch resources.
Also inconsistent behaviour between different managed applications is never good. Therefore we should support the annotation on all kinds of Elastic stack resources.
The text was updated successfully, but these errors were encountered:
eck.k8s.elastic.co/disable-downgrade-validation=true
currently only supports Elasticsearch. This is documented here https://www.elastic.co/guide/en/cloud-on-k8s/master/k8s-common-problems.html#k8s-common-problems-version-downgradeHowever if a user made a mistake an upgrade to the wrong version or a downgrade is made necessary for other reasons (bug!) it is to be expected that all related resources have already been upgraded to the new version.
Currently this make the downgrade process hard because you have to scale down the operator or disable the validating webhook to force the downgrade on the non-Elasticsearch resources.
Also inconsistent behaviour between different managed applications is never good. Therefore we should support the annotation on all kinds of Elastic stack resources.
The text was updated successfully, but these errors were encountered: