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
Skaffold will sync only with pods that the file sync is enabled for and disregard everything else.
Actual behavior
Though, Skaffold seems to sync with the correct destination pod, it also reports not being able to sync with many other pods and a job which I didn't even ask it to sync with. This even includes pods from different namespace, e.g. "kube-system". This is what I'm seeing after modifying just one file publish-ad.spec.ts in default namespace. If I read the log correctly, it appears to sync in non-related pods, but skips them because they are not running at the moment.
INFO[1719] files modified: [api/test/request/ad/publish-ad.spec.ts]
INFO[1720] files modified: [api/test/request/ad/publish-ad.spec.ts]
Syncing 1 files for api.dev:fee6b6649a885c677f9ebd9b9329821ba5a6982ab97a2407f46ead41584c8ee4
INFO[1720] Copying files: map[api/test/request/ad/publish-ad.spec.ts:[/usr/src/dl/api/test/request/ad/publish-ad.spec.ts]] to api.dev:fee6b6649a885c677f9ebd9b9329821ba5a6982ab97a2407f46ead41584c8ee4
INFO[1720] Skipping sync with pod init-db-s29wm because it's not running
INFO[1720] Skipping sync with pod compose-6c67d745f6-tjnkb because it's not running
INFO[1720] Skipping sync with pod compose-api-57ff65b8c7-lvtnb because it's not running
INFO[1720] Skipping sync with pod coredns-fb8b8dccf-dbxtw because it's not running
INFO[1720] Skipping sync with pod coredns-fb8b8dccf-pq226 because it's not running
I'll remove those logs since they are misleading. We wouldn't attempt to sync with those pods anyways since they are not using any image managed by Skaffold
dgageot
added a commit
to dgageot/skaffold
that referenced
this issue
Sep 4, 2019
Expected behavior
Skaffold will sync only with pods that the file sync is enabled for and disregard everything else.
Actual behavior
Though, Skaffold seems to sync with the correct destination pod, it also reports not being able to sync with many other pods and a job which I didn't even ask it to sync with. This even includes pods from different namespace, e.g. "kube-system". This is what I'm seeing after modifying just one file
publish-ad.spec.ts
in default namespace. If I read the log correctly, it appears to sync in non-related pods, but skips them because they are not running at the moment.Information
The text was updated successfully, but these errors were encountered: