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

Point (2) in particular implies that you have to use something higher-level to orchestrate your rollouts. In order to safely rollout a new configuration, you have to:

1. Create a new `ConfigMap` with new data in it, update `Deployment`s to reference it.
2. Wait for rollout of those `Deployment`s to complete, and
3. Finally, after it succeeds, delete the old `ConfigMap`.

Why ask users to re-implement this for every new app? Why not just handle it for them?