Documentation
Introduction
Configuration
- HTTPProxy Fundamentals
 - Ingress v1 Support
 - Virtual Hosts
 - Inclusion and Delegation
 - TLS Termination
 - Upstream TLS
 - Request Routing
 - External Service Routing
 - Request Rewriting
 - CORS
 - Websockets
 - Upstream Health Checks
 - Client Authorization
 - TLS Delegation
 - Rate Limiting
 - Access logging
 - Cookie Rewriting
 - Overload Manager
 - JWT Verification
 - Annotations Reference
 - Slow Start Mode
 - API Reference
 
Deployment
- Deployment Options
 - Contour Configuration
 - Upgrading Contour
 - Enabling TLS between Envoy and Contour
 - Redeploy Envoy
 
Guides
- Deploying Contour on AWS with NLB
 - AWS Network Load Balancer TLS Termination with Contour
 - Deploying HTTPS services with Contour and cert-manager
 - External Authorization Support
 - FIPS 140-2 in Contour
 - Using Gatekeeper with Contour
 - Using Gateway API with Contour
 - Global Rate Limiting
 - Configuring ingress to gRPC services with Contour
 - Health Checking
 - How to enable structured JSON logging
 - Creating a Contour-compatible kind cluster
 - Collecting Metrics with Prometheus
 - How to Configure PROXY Protocol v1/v2 Support
 - Contour/Envoy Resource Limits
 
Troubleshooting
- Envoy Administration Access
 - Contour Debug Logging
 - Envoy Debug Logging
 - Visualize the Contour Graph
 - Show Contour xDS Resources
 - Profiling Contour
 - Contour Operator
 
Resources
- Support Policy
 - Compatibility Matrix
 - Contour Deprecation Policy
 - Release Process
 - Frequently Asked Questions
 - Tagging
 
Security
Contribute
Visualizing Contour’s Internal Object Graph
Contour models its configuration using a directed acyclic graph (DAG) of internal objects.
This can be visualized through a debug endpoint that outputs the DAG in
DOT format.
To visualize the graph, you must have
graphviz installed on your system.
To download the graph and save it as a PNG:
# Port forward into the contour pod
$ CONTOUR_POD=$(kubectl -n projectcontour get pod -l app=contour -o name | head -1)
# Do the port forward to that pod
$ kubectl -n projectcontour port-forward $CONTOUR_POD 6060
# Download and store the DAG in png format
$ curl localhost:6060/debug/dag | dot -T png > contour-dag.png
The following is an example of a DAG that maps http://kuard.local:80/ to the
kuard service in the default namespace:

Twitter
Slack