bug: The getImageInfoByValue chart method overrides scoped parameters with global registry setting

[kuwv]

When defining global.imageRegistry the getImageInfoByValue will override defined scoped parameters with global registry settings instead.

charts: jfrog-platform => artifactory

    global:
      imageRegistry: registry.example.com
    artifactory:
      nginx:
        image:
          registry: releases-docker.jfrog.io
          repository: jfrog/nginx-artifactory-pro

resulting:

kind: pod
spec:
  containers:
  - image: registry.example.com/jfrog/nginx-artifactory-pro:7.104.12

https://github.com/jfrog/charts/blob/master/stable/artifactory/templates/_helpers.tpl#L228

[RobinDuhan]

Hello @kuwv, this is not a bug and is by design. I understand it's not as intuitive. To allow for different registry with different containers, you'd have to remove global.registry, and add individual image.registry for all containers.

[kuwv]

Thanks @RobinDuhan, I read the logic and figured out what was happening.

I understand that this is intentional decision, but it also does not follow variable precedence either: https://github.com/helm/helm/pull/12480

[RobinDuhan]

I get that completely @kuwv . We are discussing internally to see if it's feasible for us to change the ahderence to the discussed precedence now. But I wouldn't be able to say with certainty that we'd be update this any time soon.