Andrew J. Brown

Results 2 comments of Andrew J. Brown

We are still seeing this with `v0.19.8` if/when the locks are deleted from the underlying storage (i.e. no GH comments indicating the locks were deleted via the UI)

We're also experiencing this, when managing rollouts via ArgoCD. If we use `kubectl apply -f rollout.yaml`, then change the image tag and finally `kubectl apply -f rollout.yaml --server-side`, rollouts work...