Application: cannot override a single image with a custom registry
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Angie Wang |
Bug Description
Brief Description
-----------------
There is a logic in sysinv to always prepend docker registry to the image reference if the registry of the image is not in any of the known registries. This is a limitation for users to override a single image with a custom registry.
The following logic in sysinv/
# If the image is not from any of the known registries
# (ie..k8s.gcr.io, gcr.io, quay.io, docker.io. docker.elastic.co)
# or no registry name specified in image tag, use user specified
# docker registry as default
registry = self.registries
registry_auth = self.registries
registry_name = pub_img_
if registry:
% registry_name)
return registry + '/' + pub_img_tag, registry_auth
Severity
--------
Major
Steps to Reproduce
------------------
- system application-upload stx-openstack.tgz
- system helm-override-
- system application-apply stx-openstack
Expected Behavior
------------------
Image mycustomregistr
Actual Behavior
----------------
The system is trying to download docker.
stx.4.0 / medium priority - allows better flexibility for custom registries