Open yurchenkosv opened 2 years ago
@yurchenkosv Thanks for the fix. Looks like this is an issue in v1 skaffold versions. I am not sure how the PR you have fixes the issue. Can you please explain more?
Would be great if it was possible to easily pull the kaniko executor image and busybox initImage from a private registry that requires authentication. I am in a similar situation. The possibility to provide image pull secrets in skaffold.yaml would be enormously helpful.
One small hint: build.cluster.serviceAccount allows for specifying a non default service account. As a workaround one can specify a service account with an image pull secret connected.
Expected behavior
Successful build
Actual behavior
ImagePullBackOff in k8s cluster when skaffold build with kaniko
Information
Steps to reproduce the behavior