contour

Describe the bug

The documentation and some tests uses gw.ns(.svc.cluster.local) for gateways.

I think this is the correct format for istio gateways: <gateway namespace>/<gateway name>

Like here:

https://github.com/fluxcd/flagger/blob/273b05fb24d467c10939389218e6a8ec26d4c70e/test/istio/test-delegation.sh#L41

re. https://istio.io/latest/docs/reference/config/networking/virtua

The "Introduction to Contour" link on the projectcontour.io landing page points to a blog from 2019 that references Contour v0.10, this link should be updated to point to something newer, or perhaps we could drop that entire section as it seems somewhat redundant with other ways to navigate the site.

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.

Please describe the problem you have
[A clear, concise, description of the problem you are facing. What is the problem that feature X would solve for you?]
Currently, it seems that everything needed to build this project is present but the official image is about one year old.
I would propose that:

• the image gets rebuild whenever there is a change to the code -> tag latest
• tagged