You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use the connect ui in a Kubernetes setup where a sidecar of the connect-ui is notified when a new connect cluster joins. This sidecar updates then the caddy server configuration (mostly proxy settings).
Unfortunately, the caddy server does not restart automatically in case of config changes.
Proposal: use a tool like inotifywait that listens on changes of the caddy config and restart the server using "pkill -USR1 caddy
If you consider this useful as well, I could create a PR for this.
The text was updated successfully, but these errors were encountered:
We use the connect ui in a Kubernetes setup where a sidecar of the connect-ui is notified when a new connect cluster joins. This sidecar updates then the caddy server configuration (mostly proxy settings).
Unfortunately, the caddy server does not restart automatically in case of config changes.
Proposal: use a tool like
inotifywaitthat listens on changes of the caddy config and restart the server using"pkill -USR1 caddyIf you consider this useful as well, I could create a PR for this.
The text was updated successfully, but these errors were encountered: