You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once a profile is activated, the specified build, test and deploy configuration in it will be laid onto, but won’t completely replace, the build, test and deploy sections declared in the main section of skaffold.yaml.
This seems kinda ambiguous but it seems like set intersection is probably the most intuitive way this could work
a clonable repository with the sample skaffold project
skaffold dev -p cool
Generating tags...
- cool -> cool:latest
Some taggers failed. Rerun with -vdebug for errors.
Checking cache...
- cool: Found Locally
Tags used in deployment:
- cool -> cool:4b786b30fdaa5bb77cdab2e3493d8e85e811c6940a52d32840fd9d12d3ec62e1
Starting deploy...
Loading images into kind cluster nodes...
- cool:4b786b30fdaa5bb77cdab2e3493d8e85e811c6940a52d32840fd9d12d3ec62e1 -> Found
Images loaded in 92.475125ms
- pod/bootstrap created
Waiting for deployments to stabilize...
- pods: container bootstrap is waiting to start: bootstrap can't be pulled
- pod/bootstrap: container bootstrap is waiting to start: bootstrap can't be pulled
- pods failed. Error: container bootstrap is waiting to start: bootstrap can't be pulled.
Cleaning up...
- pod "bootstrap" deleted
1/1 deployment(s) failed
The text was updated successfully, but these errors were encountered:
Expected behavior
If I specify a
builds:
section under a profile I expect it to be merged into the top-levelbuilds:
sectionActual behavior
It seems to override the top-level builds
The docs on profiles say
This seems kinda ambiguous but it seems like set intersection is probably the most intuitive way this could work
Information
v2.13.2
Dockerfile:
k8s.yaml:
Steps to reproduce the behavior
skaffold dev -p cool
The text was updated successfully, but these errors were encountered: