Closed KoltesDigital closed 2 years ago
@KoltesDigital was this using k3d? There was a recent regression where Skaffold would not properly loading images into k3d and kind clusters. This root cause here is a dupe of https://github.com/GoogleContainerTools/skaffold/issues/7992, follow the issue there for more info/discussion. This should be resolved now @ HEAD with https://github.com/GoogleContainerTools/skaffold/pull/8007 and will be available in our next release to be released later this week
From the log lines
-kube-context k3d-something
and the issue being related to unable to pull images (STATUSCHECK_IMAGE_PULL_ERR
) I believe the cause here is identical to #8022. Closing this as this is resolve now @ HEAD
I've been trying for the past days to deploy / dev with Helm manifests. Although the steps are different, it may be a duplicate of #8020.
This occurs even on https://github.com/GoogleContainerTools/skaffold/tree/main/examples/helm-deployment!
Expected behavior
With the above example folder,
skaffold dev
should work.Actual behavior
Well it doesn't, see log below.
I believe the error lies in these two lines:
skaffold
does not respect the contract Helm is expecting from a post-renderer, which is, a command which takes YAML in STDIN and generates YAML on STDOUT.skaffold
doesn't care about STDIN, it only shows Skaffold's help text.I think the actual command to use as post-renderer is
skaffold render
.Information
curl -Lso skaffold https://storage.googleapis.com/skaffold/releases/latest/skaffold-linux-amd64 && install skaffold /usr/local/bin/
Steps to reproduce the behavior
out.log: