Implement rolling updates of config/secrets directly on services #9

New issue

Closed

opened 2023-08-13 20:43:22 +02:00 by so-rose · 1 comment

so-rose commented

2023-08-13 20:43:22 +02:00

Owner

Currently we stop/start stacks to perform updates of configs/secrets. This is bad :)

With a little information-gathering, I'm certain we can prevent actually stopping stacks on deploy and instead only do the secret rotation as described in the Docker documentation: https://docs.docker.com/engine/swarm/secrets/#example-rotate-a-secret

Note rolling_updates in the docker_config ansible module.

That would also allow us to make use of built-in rolling config/secret update strategies in the deploy: section of the Compose specification.

NOTE: The rclone volume stuff is always gonna need manual stop/start. Is jank. Such is life. Best we can do is make working with this more ergonomic in our playbooks.

Currently we stop/start stacks to perform updates of configs/secrets. This is bad :) With a little information-gathering, I'm certain we can prevent actually stopping stacks on deploy and instead only do the secret rotation as described in the Docker documentation: https://docs.docker.com/engine/swarm/secrets/#example-rotate-a-secret - Note `rolling_updates` in the `docker_config` ansible module. That would also allow us to make use of built-in rolling config/secret update strategies in the `deploy:` section of the Compose specification. **NOTE**: The rclone volume stuff is always gonna need manual stop/start. Is jank. Such is life. Best we can do is make working with this more ergonomic in our playbooks.