Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-11060

ImagePullPolicy inconsistent between Containers and InitContainers

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • 3scale Operator
    • False
    • None
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started

      When deploying 3scale via the operator, the `ImagePullPolicy` is not configured consistently across `Containers` and `InitContainers`. It appears that we hard code this value as `PullIfNotPresent` in the Containers but we do not specify it for the `InitContainers` so it defaults to `Always`.

      This can be problematic when deploying in a disconnected environment.

      In addition, Production environments have some benefit from using `PullIfNotPresent`. If the registry is down, the `Always` in the `InitContainers` can cause the pod to fail to come up.

      Ideally, these would be both be consistent and configurable from the APImanager/APIcast CRDs.

       

       

              Unassigned Unassigned
              rhn-support-spoole Shannon Poole
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: