Hello everyone,
I've deployed v9.1 of the helm chart. Because global.image.registry is empty, the registry is not set for the container image, even if the registry was defined under image.registry, for example. I think the issue here is due to the coalesce in the template function.
|
{{- printf "%s/%s:%s" (coalesce .Values.global.image.registry .Values.image.registry) .Values.image.repository .Values.image.tag -}} |
Kubernetes environments that rely on cri-o have been encountering an error since version 1.34 because no default registry such as docker.io is defined. This change was introduced in version 1.34 of kubernetes/crio. With this change and the usage of unqualified images environments throw the following issue:
spec.containers{nextcloud}: Failed to inspect image "": rpc error: code = Unknown desc = short-name "library/nextcloud:32.0.1-apache" did not resolve to an alias and no unqualified-search registries are defined in "/etc/containers/registries.conf"
Please fix the error by adjusting the template function or assigning a value to global.image.registry.
To prevent this error in the future, Helm unit tests would be a suitable solution.
Best regards,
Volker
Hello everyone,
I've deployed v9.1 of the helm chart. Because
global.image.registryis empty, the registry is not set for the container image, even if the registry was defined underimage.registry, for example. I think the issue here is due to thecoalescein the template function.helm/charts/nextcloud/templates/_helpers.tpl
Line 46 in 682ce2f
Kubernetes environments that rely on cri-o have been encountering an error since version 1.34 because no default registry such as
docker.iois defined. This change was introduced in version 1.34 of kubernetes/crio. With this change and the usage of unqualified images environments throw the following issue:Please fix the error by adjusting the template function or assigning a value to
global.image.registry.To prevent this error in the future, Helm unit tests would be a suitable solution.
Best regards,
Volker