Closed keithpine closed 2 years ago
The Jira issue recommends that the imagePullPolicy
should be set to Always
. Is that still the case? If so, I'd suggest it should be done in the deployment script.
The Jira issue recommends that the
imagePullPolicy
should be set toAlways
. Is that still the case? If so, I'd suggest it should be done in the deployment script.
The Always
default was intended when the container image tag was listed as latest
in older versions of cortx-k8s. Based on the evolution to use specific tagged versions, I think we are good to use the default of IfNotPresent
now.
Description
Add global values to the Helm Chart for image settings. This makes interacting with Helm simpler.
Set all containers (except Consul) to use a private container registry:
Set all of the CORTX containers (not dependencies) to use a private container registry:
Set all of the CORTX containers to use an image tag with a private registry:
Configure all CORTX Pods with an
imagePullPolicy
ofAlways
:Upgrade the CORTX image tags on an installed chart:
Type of change
Applicable issues
How was this tested?
Deployed with custom values.
helm template
with different combinations.(These would be good as unit tests)
Test file:
Default images, based on Chart.AppVersion and sub-chart defaults:
Set Global registry, affects Bitnami and CORTX images:
Set CORTX image registry and tag, only CORTX images affected:
Set CORTX image pull policy
Default:
Set to
Always
:Additional information
Alternate values format considered:
Checklist
If this change requires newer CORTX or third party image versions:
image
fields in solution.example.yaml have been updated to use the required versions.appVersion
field of the Helm chart has been updated to use the new CORTX version.If this change addresses a CORTX Jira issue:
CORTX-XXXXX:
)View rendered charts/cortx/README.md