This message was deleted.

sparse-intern-71089

09/13/2019, 6:19 PM

This message was deleted.

creamy-potato-29402

09/13/2019, 6:22 PM

@full-dress-10026 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

creamy-potato-29402

09/13/2019, 6:23 PM

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.

creamy-potato-29402

09/13/2019, 6:23 PM

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

full-dress-10026

09/13/2019, 6:24 PM

I think the deployment gets entirely replaced.

Copy code

+-  ├─ kubernetes:apps:Deployment  model-updater-deployment     replace     [diff: ~metadata,spec]
 +-  └─ kubernetes:apps:Deployment  model-executor-deployment    replace     [diff: ~metadata,spec]

creamy-potato-29402

09/13/2019, 6:24 PM

what did you change

creamy-potato-29402

09/13/2019, 6:25 PM

like, what’s the diff

full-dress-10026

09/13/2019, 6:26 PM

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

creamy-potato-29402

09/13/2019, 9:08 PM

@full-dress-10026 yes please!

creamy-potato-29402

09/13/2019, 9:09 PM

that should not trigger a replacement.

creamy-potato-29402

09/13/2019, 9:12 PM

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.

👍 1

full-dress-10026

09/13/2019, 9:19 PM

Thanks!

Open in Slack

Previous Next

Pulumi Community

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.