contour
contour copied to clipboard
projectcontour
Contour is a Kubernetes ingress controller using Envoy proxy.
I specified this proxy: ```YAML apiVersion: projectcontour.io/v1 kind: HTTPProxy metadata: name: artifactory-v2 spec: routes: services: - name: artifactory-prod port: 80 weight: 95 - service: artifactory-dev port: 80 weight: 4 -...
Header Contains conditions that result in a regex matcher are not tested. Tests at the `internal/contour` and `internal/featuretest` level should be added.
Currently, contour simply sets the panic threshold to 0 which means that if all backend pods report as unhealthy, incoming traffic will fail with a 503. For my use case...
**Please describe the problem you have** We have the AWS specifics embedded in the "getting started guide", but there are other docs on how to enable AWS/GKE (and need more)....
When you are looking at Contour deployments in a Kubernetes cluster, it's not always obvious which release you have. When we generate the deployment YAML, we could apply standard [application...
When we build a bootstrap cluster in `internal/envoy/bootstrap.go`, they have hard-coded Cluster settings that can go out of sync with the settings we use for service clusters. There's an argument...
There should be compensating controls that ensure when a HTTPProxy TCPProxy is processed we never overwrite the TCPProxy value on the resulting securevirtualhost. But that's not stated explicitly, or tested,...
There are four copies of the logic to detect inclusion / delegation loops. It should be factored out.
The gRPC stats middleware added in #1692 shows all Contour connections as completing with an 'Unknown' code. This issue is to investigate why that is. The numbers appear correct (that's...
We have a need for geo-location of incoming client requests for application routing decisions. Contour supports source IP preservation in various ways, including the `PROXY` protocol. We think we can...
Metadata
Owner
Metadata
Contour is a Kubernetes ingress controller using Envoy proxy.