StatefulSet deployed via a Flux HelmRelease are not displayed in the UI.

[pmialon]

Hi,

We use flux 2.2.3 and Flamingo v2.10.2+81e8dc2.dirty

We use flamingo generate-app to create the argo app. It work perfectly well for HelmRelease containing a Deployment but for HelmRelease containing StatefulSet everything is displayed in the Flamingo UI except the StatefulSet.

Regards,

[ThatGinger135]

I am also having resources not showing when using flamingo generate-app from a helm-release. I am using the ingress-nginx chart. The resources used to show when creating the app (this stopped showing yesterday, and I have tried redeploying it all). All that is shown in the UI is the helmReop and helmRelease objects, but nothing else (the resources are created in Kubernetes)

[rehabyte]

Same Problem here. Tried a lot of HelmCharts with different kind of resources but they won't be shown. We are using flux 2.3.0 and Flamingo v2.10.5-fl.23-main-5958964b

[hirenko-v]

Same here, we use flamingo v2.10.2-fl.23-main-d2c9a8cb and flux 2.3.0. Is there any way to display pods/deployments and other resources deployed by helm releases?

[jan-delaet]

Also having the same problem of only the HelmRelease object being shown in the UI but not the objects that are managed by said HelmRelease.

Interestingly enough, if you turn on orphaned resources detection in the associated Argo project it shows that the application contains a bunch of orphaned resources, presumably the ones that are not shown in the UI.

In all the demos I have watched about Flamingo it shows that it is possible for a HelmRelease object to render its child objects, curious what changed now to no longer make this possible?

[gopaljayanthi]

I scaled down all pods (except redis) in argocd namespace, then scaled them up, now I am able to see the pods created by helmreleases and kustomizations. I am using 2.10.5 release of flamingo.

[rehabyte]

If you downgrade flux to version 2.2.2 the resources will be shown in Flamingo (v2.10.5-fl.23-main-5958964b).