Yes. Please refer to my use case as outlined here.
At start time, a Caddyfile in the static container will configure Caddy. At runtime (sometime later), a dynamically generated Caddyfile compiled in the supervisor container will update Caddy’s configuration in static via the Configuration API and the POST /load endpoint.
I should say, this will all be running in Kubernetes…