Versions (relevant - OpenSearch/Dashboard/Server OS/Browser):
OpenSearch Dashboard:2.19.2, Issue with Helm Chart: 2.30.0
Describe the issue:
In the current OpenSearch Dashboards Helm Chart (version 2.30.0), the Docker image configuration only supports a single repository field that includes both the registry URL and the repository path. This approach is limiting, especially when compared to the OpenSearch Helm Chart, which allows separating the registry and repository using dockerRegistry and repository fields.
Current Limitation in OpenSearch Dashboards Chart:
opensearch-dashboard:
imagePullSecrets:
image:
repository: my.artifactory.url.com/docker-registry/opensearchproject/opensearch-dashboards
tag: 2.19.2
pullPolicy: IfNotPresent
In this format, the full image path must be embedded in the repository field, which reduces flexibility and deviates from the pattern used in the OpenSearch chart.
–set opensearch-dashboards.image.repository=<PVT_REG_URL>/docker-registry/opensearchproject/opensearch-dashboards
Desired Configuration (More Flexible):
opensearch-dashboard:
imagePullSecrets:
image:
registry: my.artifactory.url.com
repository: docker-registry/opensearchproject/opensearch-dashboards
tag: 2.19.2
pullPolicy: IfNotPresent
This structure would allow better alignment with private registries and CI/CD pipelines that manage registry and repository separately.
–set opensearch-dashboards.image.registry=<PVT_REG_URL>
–set opensearch-dashboards.image.repository=docker-registry/opensearchproject/opensearch-dashboards
Reference: OpenSearch Helm Chart (Working Example):
opensearch:
global:
dockerRegistry: my.artifactory.url.com
imagePullSecrets:
image:
repository: docker-registry/opensearchproject/opensearch
tag: 2.19.2
pullPolicy: IfNotPresent
–set opensearch.global.dockerRegistry=<PVT_REG_URL> #for both opensearch image and busybox image
Request:
Please consider updating the OpenSearch Dashboards Helm Chart to support separate registry and repository fields, similar to the OpenSearch Helm Chart. This would enhance consistency and flexibility for users deploying from private registries.