Uploaded image for project: 'Network Observability'
  1. Network Observability
  2. NETOBSERV-690

Proper image pinning in CSV and CRD

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • None
    • None
    • NetObserv - Sprint 227, NetObserv - Sprint 228
    • None
    • None
    • None

      Related conversation: https://chat.google.com/room/AAAANk3ECNM/nmv9u0w0BaY

      Part 1: properly pin operator image in bundle midstream.

      Use image pinning (https://docs.engineering.redhat.com/display/CFC/Digest_Pinning ) to allow that the operator image referenced from the operator-bundle is registry-proxy... before the proxy is released and in the public release is automatically set to registry.redhat.io...

      Part 2: properly pin operand images.

      From "Best Practices" document https://docs.engineering.redhat.com/display/CFC/Best_Practices :

      Images to be used for operands MUST be in the relatedImages field and SHOULD be in environment variables to the operator.

      I'll check how we can change this so we can get it for GA. I'll add  JIRA issue to track the progress on that.
      Then QE can test them according to this document: https://docs.engineering.redhat.com/display/CFC/Test

      Check e.g. how external dns resolver resolves the operand images: https://gitlab.cee.redhat.com/cpaas-midstream/external-dns-operator/-/blob/ext-dns-optr-1.0-rhel-8/distgit/containers/external-dns-operator-bundle/render_templates

       

       

              mmaciasl@redhat.com Mario Macias (Inactive)
              mmaciasl@redhat.com Mario Macias (Inactive)
              None
              None
              None
              Amogh Rameshappa Devapura Amogh Rameshappa Devapura
              None
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: