Traefik appends a tls route even when tls routes are explicitly provided

[IbraAoad]

Issue

Fixes #430

Context

For every route, traefik created a duplicate route ROUTENAME-tls for the same rule and service but with additional TLS configuration. Both applied to the same rule and thus conflict, and the new ROUTENAME-tls route takes precedence over the original ROUTENAME because its name is longer.

Solution

• New Parameter: Introduce a new boolean argument raw in the interface.
• Conditional Behavior:
  • When raw is set to True, Traefik will only append TLS routes to HTTP routes.
  • TLS routes for non-HTTP protocols will not be generated, preventing the duplicate ROUTENAME-tls routes.

Testing

Tandem PR: canonical/grafana-k8s-operator#391

[dstathis]

Love all the red in this diff!

[mmkay]

Are we expecting any charms to break due to

and rely on charm authors to provide the full traefik config when relating, including any TLS configs.

?

[IbraAoad]

Are we expecting any charms to break due to

and rely on charm authors to provide the full traefik config when relating, including any TLS configs.

?

Unfortunately yes, it seems Tempo is relying on Traefik upgrading the connection, We'll have to keep the functionality and introduce a backward compatible way to allow charm authors to opt out of getting automated TLS routes and at the same time not breaking charms that depend on it.

[dstathis]

LGTM