Establish Ownership and Visibility of Helm Resources in ArgoCD via OwnerReferences

[perlinger]

What problem are you facing?

ArgoCD does not display Helm resources installed through Kind: Release.

How could Crossplane help solve your problem?

Add OwnerReferences. Adding OwnerReferences is necessary to link resources installed via Kind: Release to their respective owning resources. By doing so, the ownership relationship can be established, and the Helm resources should become visible in ArgoCD.

[bobh66]

This is possible for Release objects that deploy within the same cluster that Crossplane/provider-helm are running in, but cross-cluster ownerReferences are not supported by Kubernetes, so it wouldn't work for any Release object that is deploying into a remote cluster. I suspect that the majority of use cases for provider-helm deploy into a remote cluster (I know they are in our deployments). provider-kubernetes has similar use cases and limitations on ownerReferences.

[nu-vi]

+1 This would be a nice feature to have, despite the cross-cluster limitations