Philipp Moeller
Philipp Moeller
Can confirm. Looking at https://quay.io/repository/argoprojlabs/argocd-operator?tab=history&tag=latest v0.9.0 was overwritten ``` v0.9.0 was moved to SHA256[ 25c71c9f0fbc ](https://quay.io/repository/argoprojlabs/argocd-operator/manifest/sha256:25c71c9f0fbc5203b3ea8021cb770a98642ddf3ee3cc85faac3be642b7183491) from SHA256 38d61c3acda6 ``` The old manifest must have been deleted: https://quay.io/repository/argoprojlabs/argocd-operator/manifest/sha256:38d61c3acda6230525614d1e609d0955f944680ccf12c07c1c84a7e5b0b98de8
@reginapizza Any chance for an update soon?
@reginapizza Looks like the PR is approved but not merged yet?
@FxKu I'm not sure about that. Is the k8s version enough? Don't we also need to check for the feature flag?
I've had a short look at the situation and I'm a bit confused by the current state. ArgoCD supports almost all `helm.sh/hook` annotations: https://argo-cd.readthedocs.io/en/stable/user-guide/helm/#helm-hooks The problem seems to be the...
Any chance this is ever getting merged or is there a workaround?
@iam-veeramalla I doubt this will ever get merged as long as 4.8 is not supported, which is a real problem since this breaks updates for almost all OpenShift users.
@jonaslar I don't think so, the new PR is still not there.
4.8 is not supported anymore
@hyberdk Are you sure? This commit should have been in the version we are using but our installation still broke?