Skip to main content
Contour is a Kubernetes ingress controller using Envoy proxy, providing a powerful HTTPProxy CRD with route delegation, weighted routing, TLS termination, and TCP proxying.

​
What Radar Shows

Topology: Full Contour routing path - HTTPProxy (root) → HTTPProxy (child, via delegation) → Service, with TLS secret configuration edges. Root proxies with spec.virtualhost appear as entry points; child proxies referenced via spec.includes are connected via delegation edges. Both Resources and Traffic view modes are supported. TLS references resolve local Secret names and delegated namespace/name names consistently, including client CA/CRL and upstream validation bundles. Configuration graphs reuse cached Secret metadata even when general Secret display is disabled; unavailable metadata remains unknown. Declared references do not establish that Contour has accepted or authorized TLS delegation, and topology does not serialize Secret values.
Contour Topology

Contour in Topology View - HTTPProxy → Service routing with delegation

HTTPProxy Detail View:
  • Status banner for invalid or orphaned proxies
  • Virtual host FQDN and TLS configuration with clickable Secret links
  • Routes with prefix/header conditions and backend services (name, port, weight)
  • Delegation includes with cross-namespace indicators and condition prefixes
  • TCP proxy services for passthrough configurations
  • Status conditions (Valid/Invalid/Orphaned)
Resource Browser: Smart columns show FQDN, route count, include count, TLS status (shield icon), and validity status at a glance.

​
Supported CRDs