GoogleContainerTools / GoogleContainerTools/skaffold
Skaffold File Sync - Subsequent Pod Deploy
- Dominant language
- Go
- Stars
- 15.9k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 10
Description
### Expected behavior
Skaffold resyncs files after a breaking change causes a pod to redeploy
### Actual behavior
Skaffold doesn't do anything - it will continue to sync files to the new pod when changes are made but previous changes are ignored. I understand the files are synced to the pod rather than the container, but this requires skaffold dev to be restarted if the pod ever crashes.
### Information
- Skaffold version: v1.33.0
- Operating system: MacOS 11.6
- Installed via: Homebrew
- Contents of skaffold.yaml:
```yaml
- image: myapp
context: myapp
docker:
dockerfile: myapp.Dockerfile
sync:
infer:
- '**'
```
### Steps to reproduce the behavior
1. setup skaffold with file sync
2. once stable, make a change to trigger the file sync
3. delete the pod that the file was synced to
4. examine the new pod, the content isn't synced on pod standup
Contributor guide
Assessment
This issue has not been assessed yet.