GoogleContainerTools/skaffold

Skaffold File Sync - Subsequent Pod Deploy

Open

#6,924 opened on Dec 1, 2021

View on GitHub
 (6 comments) (6 reactions) (0 assignees)Go (1,416 forks)batch import
area/synchelp wantedkind/bugkind/frictionpriority/p3

Repository metrics

Stars
 (12,822 stars)
PR merge metrics
 (Avg merge 3d 6h) (16 merged PRs in 30d)

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:
  - 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