contour

Describe the bug

There is a bug in podinfo chart which will not deploy service if you enabled canary, even though you enabled service via helm values.

https://github.com/fluxcd/flagger/blob/main/charts/podinfo/templates/service.yaml#L1

To Reproduce

If you set values like this, it will not deploy service.

service:
  enabled: true # service will not be deployed if ca

See release notes for Envoy 1.20.0: https://www.envoyproxy.io/docs/envoy/v1.20.0/version_history/current

http: the HeaderMatcher fields exact_match, safe_regex_match, prefix_match, suffix_match and contains_match are deprecated by string_match.

The wrinkle here is that string_match was added in Envoy 1.20.0 and does not exist in 1.19.x so we cannot use this field as soon as we

Currently this system's modes are changed only when contours are appeared above the icon area but it will not always be best idea. So if anyone can train a Gesture Recognition model and then assign a mode then this will add real aid.
Thanks.

Please describe the problem you have
With #382, namespaced-scoped operands, i.e. Envoy DaemonSet, reside in the same namespace as the Contour. This allows using an OwnerReference instead of labels for managing the Contour<>operand relationship. The current CONTOUR_NS/CONTOUR_NAME label-based approach should be

Currently, the dex and gangway config files must be updated manually.

Automate this replacement. Perhaps use a templating system, ideally something less heavy-weight than helm.