search

fluxcd / flux

Successor: https://github.com/fluxcd/flux2
https://fluxcd.io
Apache License 2.0
6.9k stars 1.08k forks source link

Flux stop automatically deploy after update cert-manager version #3557

Closed jsun9406 closed 3 years ago

jsun9406 commented 3 years ago

Hello all,

Since we updated cert-manager version from v0.9 to v1.5.3 .
Flux stop deploying HelmRelease to our kubernetes cluster, even though I am not entirely sure if this issue is really related to cert-manager update as there isn't any error logs in flux or flux helm operator pod that really indicate what's stopping flux from deploying.

Does anyone has similar issue after updating cert-manager or any suggestions how to proceed troubleshooting flux not automatically deploy?

Kubernetes version that are having issue with flux not automatically deploy: 1.19.11 1.17.11

kingdonb commented 3 years ago

Please fill out the issue template with details about your Flux installation. We do not know the Flux version that you are using.

I am using Flux and cert-manager without issue together, there is no dependency between Flux and cert-manager. It sounds like you've upgraded more than just cert-manager. The current release of Flux v1 has support for up to at least Kubernetes 1.22.0, you must be on at least Flux 1.23.0 to get that support.

If you upgraded cert-manager to the latest version, that probably also means you upgraded CRD to v1. Flux v1.23.0 and Helm Operator 1.4.0 were released to handle the CRD v1 upgrade. So you might be fighting against that issue, if you haven't also made the corresponding upgrade to the latest version of Flux.

Please upgrade Flux if you are not on the latest version and let us know if it solves your issue!

kingdonb commented 3 years ago

Thanks for your report! Unfortunately without additional information, there is nothing else that we can do to follow up.

I will happily discuss this issue if it still affecting you and you need help, but I will have to close this as some follow-up questions were already posed, and there has been no response.