Laurent Lavaud

@vara-bonthu Traefik port (9000) is not exposed by default on the service so we must do the port-forward directly on the pod, but for me I still have a 404...

> @vara-bonthu > Traefik port (9000) is not exposed by default on the service so we must do the port-forward directly on the pod, > but for me I still...

It is not possible to trigger rolling update on create/update events that occurs only after the Reloader's pod has started ?

> Your PR LGTM. Not that I don't believe you, but I can't see the retries stuff actually in v2.9.0 - this is almost certainly because I can't use computers...

> I see the PR. I couldn't see it merged/released to v2.9.x - it seems to be sat on `master`. It is in the [CHANGELOG](https://github.com/argoproj/argo-cd/releases/tag/v2.9.0), weird...

> I told you I couldn't use computers :) > > Cheers for your help. no, you're right, code is not in the [2.9.0](https://github.com/argoproj/argo-cd/blob/v2.9.0/util/http/http.go#L18) compared to [master](https://github.com/argoproj/argo-cd/blob/master/util/http/http.go#L21) :(

A possible workaround: ```yaml resource.customizations.ignoreDifferences.argoproj.io_Application: | jqPathExpressions: - .metadata.finalizers[]? | select(. == "post-delete-finalizer.argocd.argoproj.io" or . == "post-delete-finalizer.argocd.argoproj.io/cleanup") - if (.metadata.finalizers | length) == 0 then .metadata.finalizers else empty end ```

@alexmt Hello, can I have your opinion on this please ? do you consider it as a bug or normal behavior ?

also experience these problems with latest version 2.10.2

> Hello, is this still expected to be merged for argocd 2.9? Hello, you mean 2.10 ?