Features06 Secrets & networks

Change a secret the swarm says you cannot.

Secrets and configs cannot change in a swarm. The app creates a new one, switches every service that uses it, and removes the old one, in one step. It shows which services use each of them, and does the same for the overlay networks of the swarm.

Fig. — Secrets, with the services that use them; the content cannot be read back.

What you can do

Create one

Create one from text or from a file, and view the content of a config. The content of a secret cannot be read back: the API never returns it.

Who uses it

Every secret and config with the services that use it.

Replace the content

The app creates name-v2, switches every service that uses it to the new one on the same path, and removes the old one.

Remove what nothing uses

Remove one once no service uses it.

Clean up after services

Removing services also offers to clean up the networks, configs and secrets that nothing else uses; secrets are not ticked by default. Named volumes stay on the nodes.

Overlay networks

Networks in the sidebar: the overlay networks of the swarm with their stack, subnet, which services use them, and whether they are attachable, internal or encrypted. The networks of the node itself (bridge, host and the like) are one tick away.

A new network

An overlay network for the whole swarm, attachable, internal or encrypted, with a subnet and gateway of your own or one from the address pool of the swarm. Attach a service to it in New service or Adjust settings.

Remove a network

Remove a network once no service uses it. The ingress network and the networks of Docker itself stay.

Several steps as one

A new password, without three commands per service.

By hand, a new value for a secret means docker secret create, a docker service update with --secret-rm and --secret-add for every service that uses it, and docker secret rm. The app does it as one action, and keeps the path inside the containers the same.

Networks

Encrypted is one tick, with the protocol it needs.

An encrypted overlay network needs IP protocol 50 (ESP) between the nodes, and the dialog says so where you tick it. A network that a service still uses cannot be removed, and a network from a stack shows its stack.

Fig. — A new encrypted overlay network, with the note on the protocol it needs.

All features

Try it on your own swarm.
Free, with the source on Codeberg. An installer for Windows 10 and 11 that installs nothing on the swarm.
Download for Windows
Version 1.8.0 · Docker-Swarm-MX-Setup.exe