In a multi config project (different skaffold.yaml files), where each config has a different deploy context (kubeContext), running skaffold dev deploys all the modules in all the contexts.
Expected behavior
Every module should be deploy in its corresponding context
Actual behavior
All the modules are deployed in all the contexts
Information
Skaffold version: v1.38.0-79-gc319fd6c3
Operating system: MacOS Monterey
Installed via: Local build using the main branch
Contents of skaffold.yaml:
We can use the example project multi-config-microservices, adding different kubeContext for each module:
Modify leeroy-app skaffold.yaml file to add a kubeContext:
Modify the skaffold.yaml files listed above to add different kubeContext
Create the context-one and context-two contexts
Run skaffold dev in the multi-config-microservices example
Check the pods deployed in each context running kubectl get pods --context=context-one and kubectl get pods --context=context-two, you'll notice that all the modules were deployed in all the contexts
In a multi config project (different
skaffold.yaml
files), where each config has a different deploy context (kubeContext
), runningskaffold dev
deploys all the modules in all the contexts.Expected behavior
Every module should be deploy in its corresponding context
Actual behavior
All the modules are deployed in all the contexts
Information
We can use the example project multi-config-microservices, adding different
kubeContext
for each module:Modify
leeroy-app
skaffold.yaml file to add akubeContext
:Modify
leeroy-web
skaffold.yaml file to add akubeContext
:The other yaml files in the example don't need a change.
Steps to reproduce the behavior
skaffold.yaml
files listed above to add differentkubeContext
context-one
andcontext-two
contextsskaffold dev
in the multi-config-microservices examplekubectl get pods --context=context-one
andkubectl get pods --context=context-two
, you'll notice that all the modules were deployed in all the contexts