Configuration via container labels

[Weasy666]

I'm currently using Traefik Proxy to expose my services/containers to the network/internet. I am setting them up via Docker Compose and configure their Traefik "routes" via container labels.
Is a configuration via container labels with service autodiscovery, like Traefik is doing it, planned for Zentinel?

[raffaelschneider]

Tracked as a design issue: #226.

Short version: yes, it's a real gap, no, it's not a copy-paste of Traefik. The manifesto principles ("explicit, no magic") rule out an in-process Docker SDK by default. The issue lays out four candidate shapes (control plane, external agent, native built-in, sidecar generator) and recommends starting with a sidecar that watches the Docker socket and writes KDL fragments to /etc/zentinel/conf.d/. The proxy already supports multi-file config and SIGHUP reload, so the generated routing state stays on disk where you can cat it, diff it, and check it into git.

Feedback welcome on the issue, especially on:

• Label namespace (zentinel.* vs shorter)
• Mirror Traefik's label schema for migration ease, or design a leaner KDL-native one?
• Where parse errors should surface (file, metric, admin endpoint)

No code lands until the shape is settled.