|
We have several helmchart and helmrelease resources existing in a k8s cluster, all in state Ready. Now the problem description: after starting the source-controller, it first marks all helmcharts as not ready (error How can this situation be avoided? I can imagine splitting up our flux2 helm chart into separate ones (1 for source-controller, 1 for helm-controller) and thereby deploying both controllers sequentially could help, or use helm hooks to deploy them sequentially. |
Replies: 1 comment
|
Linking to the issue where we are tracking this, I've replied there (it's not an identical report but it's very close, I think it may be the same root issue): |
Linking to the issue where we are tracking this, I've replied there (it's not an identical report but it's very close, I think it may be the same root issue):
fluxcd/source-controller#924