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
cd examples/nodejs
skaffold run
cd ../../examples/react-reload
skaffold dev -v debug 2>&1 | grep Register
It shows that the second run also watches the first deployment:
time="2019-07-18T13:26:16+02:00" level=debug msg="Register deployment node for status check"
time="2019-07-18T13:26:16+02:00" level=debug msg="Register deployment node-react for status check"
Deleting the first deployment with
cd examples/nodejs
skaffold delete
will eventually (after the timeout) lead to a failure of the skaffold dev run.
A possible way out would be to add a new label with a UUID that is generated in every skaffold run. In other words deployments should be selected via
Skaffold now checks the deployment status. However, the checks for multiple runs can interfere.
For example, with this patch on master:
Skaffold prints the watched deployments.
When doing
It shows that the second run also watches the first deployment:
Deleting the first deployment with
will eventually (after the timeout) lead to a failure of the
skaffold dev
run.A possible way out would be to add a new label with a UUID that is generated in every skaffold run. In other words deployments should be selected via
in
pkg/skaffold/deploy/status_check.go:80
,cc @tejal29
The text was updated successfully, but these errors were encountered: