<p>I have a microservice application in one repo that communicates with another service that's managed by another repo.
This is not an issue when deploying to cloud, however, when devving locally the other service needs to be deployed too.</p>
<p>I've read this documentation: <a href="https://skaffold.dev/docs/design/config/#remote-config-dependency" rel="nofollow noreferrer">https://skaffold.dev/docs/design/config/#remote-config-dependency</a> and this seems like a clean solution, but I only want it to depend on the git skaffold config if deploying locally (i.e. current context is &quot;minikube&quot;).</p>
<p>Is there a way to do this?</p>

<p>Profiles can be <a href="https://skaffold.dev/docs/environment/profiles/#activation" rel="nofollow noreferrer">automatically activated</a> based on criteria such as environment variables, kube-context names, and the Skaffold command being run.</p>
<p>Profiles are processed after resolving the config dependencies though.  But you could have your remote config include a profile that is contingent on a <code>kubeContext: minikube</code>.</p>
<p>Another alternative is to have several <code>skaffold.yaml</code>s: one for prod, one for dev.</p>
