Skip to content

relatedimages issue in olm #1643

@zlcnju

Description

@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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesthelp wantedExtra attention is neededolmIssue related to the Operator Lifecycle Managerpriority: low

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions