Expected behavior Running skaffold dev should start the stack Actual behavior creating container in local docker: Error response from daemon: Ports are not available: exposing port TCP 127.0.0.1:9000 -> 0.0.0.0:0: listen tcp 127.0.0.1:9000: bind: Only one usage of each socket address (protocol/n...

Issue tracks known bug where skaffold verify "no duplicate names" validation currently doesn't properly handle multiple modules

Expected behavior Expect to see an image named workflow_local, Actual behavior Image url is incorrect. Information Missing documentation image on public website. Steps to reproduce the behavior Visit https://skaffold.dev/docs/design/

A Skaffold project configured with the cloudrun deployer, that deploys more than one Cloud Run service in a single module, only streams the logs from one of those services, the others are not printed in the console. This works as expected when we have more than one module, each with one Cloud Run se...

Reproduction steps Have a top-level skaffold.yaml which requires other configs and has verify section. apiVersion: skaffold/v4beta1 kind: Config metadata: name: accounts requires: - configs: - contacts path: contacts/skaffold.yaml - configs: - userservice path: userservice/skaffold.yaml...

Trying to migrate v2 to v3 with about 40+ microservices. If I comment out more microservices, the startup time gets faster. Definitely a correlation there. Expected behavior Should see logs almost immediately to see what's happening Actual behavior No logs for about 1.5 minutes. Information Skaffol...

Expected behavior Actual behavior Information Skaffold version: v2.0.4 Operating system: Linux Debian 5.19.11-1rodete1 Installed via: curl -Lo skaffold https://storage.googleapis.com/skaffold/releases/latest/skaffold-linux-amd64 && sudo install skaffold /usr/local/bin/ Contents of...

It seems that for some users the skaffold update check is not appearing at the intervals that are most beneficial UX wise. Need to investigate more, will update the message here w/ more info when available

Most of our time is spent waiting for helm chart render and deployment to run one by one (this is exceptionally problematic when deploying/rendering tasks is taking a few minutes). We could significally reduce deployment time by processing the required skaffold files in parallel. Expected behavior W...

Issue tracks updating skaffold integration/examples and examples that use go 1.18 in places and to be upgraded to using go 1.19 to make them more up-to-date and consistent across all examples