magnificent-dress-2749402/17/2023, 11:30 PM
cluster that docker.io images that should not require pull secrets fail with a 401 authorization error. Example:
I noticed the same thing with a JupyterHub deployment. I eventually got around that by adding my Docker Pro credentials and specifying
helm upgrade --install openfaas openfaas/openfaas -n openfaas -f values-arm64.yaml --- 29s Warning Failed pod/nats-7489f6b794-7qfjs Failed to pull image "nats-streaming:0.25.3": rpc error: code = Unknown desc = failed to pull and unpack image "<http://docker.io/library/nats-streaming:0.25.3|docker.io/library/nats-streaming:0.25.3>": failed to resolve reference "<http://docker.io/library/nats-streaming:0.25.3|docker.io/library/nats-streaming:0.25.3>": failed to authorize: failed to fetch oauth token: unexpected status: 401 Unauthorized
as the Chart allows. Unfortunately, the OpenFaaS does not allow for specifying
for the base install. Does anybody have any tips on this? I haven't had to specify credentials for both of these deployments in the past. This seems to have only come up in the past few weeks.