Skaffold: Skaffold run is not idempotent anymore

[balopat]

Since runId was introduced now k8s resources are recreated.
We should think about carefully how to enable idempotent behavior again.

[dgageot]

Idempotency is crucial if skaffold run is used in a git ops environment or if causing downtime is a no-go.

It's also important that running skaffold dev doesn't take what's already running down because it consumes time and can make the user think that something is broken on their code.

[guilhem]

I'm quite surprised to see this issue as "closed".

skaffold run is not idempotent, there is just a workaround to make it possible with a flag that must be set carefully by user.

Right now this behavior is dropping all my statefulset at each run... not really a good default behavior...

[Nuke1234]

Hello!

The issue with the Skaffold labels is still present. It breaks the semantic of kubectl apply and is a show stopper of using Skaffold for deploying. It makes no sense that metadata of a tool used in the deployment process triggers a restart of the pods.

Maybe annotations instead of labels would be the proper place to put this kind of information

[tejal29]

Reopening issue.

[briandealwis]

@nkubala still on track for 1.16.0?

[nkubala]

mmmm i'll try and get my PR back open this week, otherwise i'll bump the milestone.

[tejal29]

Keeping the priority same though it's making triage unhappy.