You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The dockerConfig.secretName and pullSecretName are only mounted inside the kaniko pod, if i understand correctly. The use case described by me would require a pull secret for the kaniko images itself.
a private container registry at private.registry.com that requires token authentication for pulling images
skaffold build
time="2023-11-10T10:35:02+01:00" level=info msg="Waiting for kaniko-m8x5s to be initialized" subtask=private.registry.com/myapp task=Build copying sources: waiting for pod to initialize: context deadline exceeded
The text was updated successfully, but these errors were encountered:
Expected behavior
Pull the kaniko image and imitImage from a private registry with pull secret credentials
The private registry requires an
imagePullSecret
for the kaniko pod specThe
dockerConfig.secretName
andpullSecretName
are only mounted inside the kaniko pod, if i understand correctly. The use case described by me would require a pull secret for the kaniko images itself.For my personal use case, it would solve the issue if the
cluster.pullSecretName
was also added to the kanikoPodSpec
:Could that be added as a general option?`What do you think?
Actual behavior
Failed to pull image "private.registry.com/k8s-skaffold/skaffold-helpers/busybox": rpc error: code = Unknown desc = failed to pull and unpack image "private.registry.com/k8s-skaffold/skaffold-helpers/busybox": failed to resolve reference "private.registry.com/k8s-skaffold/skaffold-helpers/busybox": failed to authorize: failed to fetch anonymous token:
unexpected status: 401
Information
Steps to reproduce the behavior
private.registry.com
that requires token authentication for pulling imagesskaffold build
The text was updated successfully, but these errors were encountered: