Add note about overriding kubecontext in profiles.
@@ -79,6 +79,7 @@ It should also be possible to specify in various places:
#### Option in `skaffold.yaml`
A configuration option in `skaffold.yaml` has the advantage of being most discoverable:
it is in the place where users configure all aspects of their pipeline.
+In addition, it allows to define the kubecontext per Skaffold profile.
However, it also has questionable implications:
@@ -90,7 +91,7 @@ However, it also has questionable implications:
This profile activates a different kubecontext `B`.
A solution could be to forbid specifying a kubecontext in a profile if it is activated by a kubecontext (and validate that).
-The best place for the config in `skaffold.yaml` is in `latest.DeployConfig`, resulting in a json path `deploy.kubeContext`.
+A natural place for the config in `skaffold.yaml` is in `latest.DeployConfig`, resulting in a json path `deploy.kubeContext`.
#### Option in global Skaffold config
Specifying a default kubecontext globally is straightforward. For example, via new config option
