relatedimages issue in olm

[zlcnju]

I'm using ArgoCD from OperatorHub in a private/air-gapped environment and need to know which images should be synced to my private registry. This information should be defined in the relatedImages section of the CSV (ClusterServiceVersion), but the ArgoCD operator currently lacks this definition.

This makes it challenging to:

1. Identify all required images for air-gapped installations
2. Ensure all necessary images are mirrored to private registries
3. Deploy ArgoCD operator reliably in disconnected environments

Could we add the missing relatedImages section to properly document all required images for the ArgoCD operator?

This would help users in private/air-gapped environments to properly prepare their environments for ArgoCD deployment.

[svghadi]

Thanks @zlcnju. Yes. It makes sense to list all required images under relatedImages section to facilitate easy installation in disconnected env.

Contributions are welcomed to resolve this. :)

In the meantime, if you are blocked, you can find all the required images for v0.13.0 in

• https://github.com/argoproj-labs/argocd-operator/blob/v0.13.0/common/defaults.go

• argocd-operator/deploy/olm-catalog/argocd-operator/0.13.0/argocd-operator.v0.13.0.clusterserviceversion.yaml

  Line 1904 in f8e6b0f

  image: quay.io/argoprojlabs/argocd-operator@sha256:d7f62482426bd8a1ff99f193f199b11e295a1f9093a8b65fa14ada7eec77e1a3