Uploaded image for project: 'Red Hat Internal Developer Platform'
  1. Red Hat Internal Developer Platform
  2. RHIDP-5838

[Helm] test-connection pod Image is hardcoded, which can be an issue in air-gapped environments [1.4.2]

Create Doc EPIC for Fe...Prepare for Y ReleasePrepare for Z ReleaseXMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 1.4.2
    • 1.3.0, 1.4.0, 1.4.1
    • Helm Chart
    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      In the previous versions of the {product-short} Helm Chart, it was not possible to configure the image for the `test-connection` pod, which could be a problem for air-gapped environments.
      The `test-connection` pod is a Pod created by the Helm Chart when a user runs the `helm test` command to test a deployed Release.
      This issue has been fixed by making the image configurable and also allowing disabling the `test-connection` pod creation altogether. The following fields are now exposed in the Helm Chart:

      [source,yaml]
      ----
      # -- Test pod parameters
      test:
        # -- Whether to enable the test-connection pod used for testing the Release using `helm test`.
        enabled: true

        image:
          # -- Test connection pod image registry
          registry: quay.io

          # -- Test connection pod image repository. Note that the image needs to have both the `sh` and `curl` binaries in it.
          repository: curl/curl

          # -- Test connection pod image tag. Note that the image needs to have both the `sh` and `curl` binaries in it.
          tag: latest
      ----
      Show
      In the previous versions of the {product-short} Helm Chart, it was not possible to configure the image for the `test-connection` pod, which could be a problem for air-gapped environments. The `test-connection` pod is a Pod created by the Helm Chart when a user runs the `helm test` command to test a deployed Release. This issue has been fixed by making the image configurable and also allowing disabling the `test-connection` pod creation altogether. The following fields are now exposed in the Helm Chart: [source,yaml] ---- # -- Test pod parameters test:   # -- Whether to enable the test-connection pod used for testing the Release using `helm test`.   enabled: true   image:     # -- Test connection pod image registry     registry: quay.io     # -- Test connection pod image repository. Note that the image needs to have both the `sh` and `curl` binaries in it.     repository: curl/curl     # -- Test connection pod image tag. Note that the image needs to have both the `sh` and `curl` binaries in it.     tag: latest ----
    • Bug Fix
    • Proposed
    • RHDH Install 3268, RHDH Install 3269

      Description of problem:

      More details in https://issues.redhat.com/browse/RHDHBUGS-155 

      Prerequisites (if any, like setup, operators/versions):

      Steps to Reproduce

      1. Deploy the Helm Chart in an air-gapped environment
      2. Run `helm test $RELEASE_NAME`

      Actual results:

      The image for the test-connection pod will fail to be pulled.

      Expected results:

      As depicted in RHDHBUGS-155, the image should be configurable so that it can be mirrored into the airgapped environment.

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Build Details:

      1.3 and 1.4

      Additional info (Such as Logs, Screenshots, etc):

              rh-ee-asoro Armel Soro
              rh-ee-asoro Armel Soro
              RHIDP - Install
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: