feat: add better support and messaging around using helm with skaffold apply #7149
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 #7101
This PR makes it so that if a single helm release is specified with a namespace option and that release is the only deployment, skaffold will set the kubectl namespace to that namespace. In the case that a helm release is specified with a namespace option and another deployment exists (eg: helm + kubectl deployments) or the case that multiple helm releases with namespaces are specified,
skaffold apply
will error stating:NOTE: for this to work properly, the apply call must also specify the profile used in the render call
skaffold apply -p dev --filename=skaffold.yaml manifest.yaml
^^ This is because render does not store anywhere (skaffold state, manifest files, etc) which profile was used to generate the manifests so it needs to be passed in both places