Documentation
Introduction
Configuration
Deploy
Guides
- AWS with NLB
- Cert-Manager
- External Authorization
- JSON logging
- Migrating to HTTPProxy
- Prometheus Metrics
- PROXY Protocol Support
- Resource Limits
Troubleshoot
Resources
- Support Policy
- Envoy Support Matrix
- Kubernetes Support Matrix
- Contour Deprecation Policy
- Release Process
- Frequently Asked Questions
- Tagging
Contribute
Overview
Contour is an Ingress controller for Kubernetes that works by deploying the Envoy proxy as a reverse proxy and load balancer. Contour supports dynamic configuration updates out of the box while maintaining a lightweight profile.
Contour also introduces a new ingress API HTTPProxy which is implemented via a Custom Resource Definition (CRD). Its goal is to expand upon the functionality of the Ingress API to allow for a richer user experience as well as solve shortcomings in the original design.
Prerequisites
Contour is tested with Kubernetes clusters running version [1.16 and later][4].
RBAC must be enabled on your cluster.
Get started
Getting started with Contour is as simple as one command. See the [Getting Started][3] document.
[3]: {% link getting-started.md %} [4]: {% link _resources/compatibility-matrix.md %}