contour icon indicating copy to clipboard operation
contour copied to clipboard

Contour is a Kubernetes ingress controller using Envoy proxy.

Results 416 contour issues
Sort by recently updated
recently updated
newest added
trafficstars

**What question do you have?:** I have a problem with address rewrite. I installed contour with TLS Delegation on Kubernetes 1.26 Everything work fine with Ingress etc. Problem is with...

kind/question
lifecycle/stale
lifecycle/needs-triage

Part of the edge best practices for running envoy, in addition to the max-heap resource monitors, there's a global connection limit set, https://www.envoyproxy.io/docs/envoy/latest/configuration/best_practices/edge#best-practices-edge > >```yaml >layered_runtime: > layers: > -...

kind/feature
lifecycle/needs-triage

Following up to https://github.com/projectcontour/contour/pull/2157#pullrequestreview-348420521, need to refactor the logic a bit in the DAG builder.

lifecycle/stale

**What steps did you take and what happened:** I have a httpProxy configured with a TCP proxy and the new field **protocol**: ``` apiVersion: projectcontour.io/v1 kind: HTTPProxy metadata: name: kubernetes...

lifecycle/stale

We should run [shellcheck](https://www.shellcheck.net) in CI on all our bash scripts.

area/testing
lifecycle/stale

## problem statement As a cluster operator, I want to enable namespace admins to "claim" a root hostname for themselves in a fully self-service way, without my involvement. I also...

blocked/needs-design
lifecycle/stale

In `internal/httpsvc/http.go`, `(*Service) Start(), there is a goroutine that is started to shutdown the service when a stop channel is signaled. If `ListenAndServe` ever returns, this goroutine will be leaked.

lifecycle/stale

**What steps did you take and what happened:** [A clear and concise description of what the bug is.] 1. Followed guide: https://projectcontour.io/docs/1.28/guides/external-authorization/ to get an external auth setup 2. Alter...

kind/bug
lifecycle/stale
lifecycle/needs-triage

**Please describe the problem you have** For integrations of Gateway API and Contour like knative's [`net-gateway-api`](https://github.com/knative-extensions/net-gateway-api), there is no great way right now to know which Envoy Service ports are...

kind/feature
lifecycle/stale
area/gateway-api
lifecycle/needs-triage
area/gateway-provisioner

Now that Contour uses the go-control-plane-based xDS server by default, migrating to [incremental/delta xDS](https://www.envoyproxy.io/docs/envoy/latest/api-docs/xds_protocol#incremental-xds) should be possible. This will make xDS communication more efficient, particularly for large clusters.

kind/feature
priority/important-soon
lifecycle/needs-triage