skip manifest validation for default kubectl deployer
#6294
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #6254
Description
In #6043 we introduced validation for the
kubectl
deployer manifests. This breaks backward compatibility for users who were usingskaffold run
without any deployer defined. Although that doesn't seem like a valid usecase for therun
command, for versions <= v1.26.0,skaffold run
command worked the same asskaffold build
command in the absense of adeployer
stanza in the skaffold config.The default deployer (
./k8s/*
) gets added when no explicit deployer is defined, which now fails the validation introduced in #6043.To keep backward compat behavior, this PR skips the manifest validations when only the default kubectl deployer is defined.