No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

After doing a `pulumi up` with my `k8s.apps.v1.Deployment`, k8s (or Pulumi?) replaced all existing pods immediately instead of replacing in a one-by-one fashion, waiting for the readinessProbe to become true. Is this something I need to configure Pulumi to do?

<@UCZ0LS7NZ> what do you mean when you say “replaced all existing pods immediately”? Do you mean the deployment was replaced or the rollout was not incremental

If the latter, that is managed b the k8s deployment controller, not pulumi. we have no ability to control it beyond what is exposed through the deployment API.

If the former, it could be a bug but we’d need to know more to say for sure.

I think the deployment gets entirely replaced.
```
+-  ├─ kubernetes:apps:Deployment  model-updater-deployment     replace     [diff: ~metadata,spec]
 +-  └─ kubernetes:apps:Deployment  model-executor-deployment    replace     [diff: ~metadata,spec]
```

I changed metadata.labels.version and the container image. I can DM the diff if that'd help.

Just looping back, this triggered a replacement because `.spec.selector` is immutable. If you change that, ever, you _must_ replace it. Kubernetes will reject any changes to this field.