Replies: 1 comment
-
@shahriak When using a private registry you'll want to make sure you are overriding the default registry values in the charts. If installing linkerd2-viz first, you'll want to override it's defaultRegistry value: This is assuming that your linkerd2 chart installation is also pointing at the private registry. linkerd2 chart has a few additional registry fields for proxy.image.name, proxyInit.image.name, and controllerImage. So the linkerd2 chart installation should pass the flag: |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I am trying to install linkerd2 and linkerd-viz components using a single Helm install command. For that I have created a requirements file and included linkerd-viz as a dependency. I am aware that linkerd core components needs to be installed before linkerd-viz components can successfully start. Therefore, I have included a post install hook to simply restart the linkerd-viz components after the linkerd check command succeeds (kubectl rollout restart deploy -n linkerd-viz). Now the issue I am running into is, the proxy-init image is not being able to be pulled from the private registry after the post install hook executes the command. I have updated the _proxy_init.tpl file under the partials folder to point to the registry as well. I am not sure what I am missing..
Error message:
Failed to pull image "proxy-init:v1.3.9": rpc error: code = Unknown desc = Error response from daemon: pull access denied for proxy-init, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
Beta Was this translation helpful? Give feedback.
All reactions