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
 - Annotations Reference
 - Cookie Rewriting
 - API Reference
 
Deployment
- Deployment Options
 - Contour Configuration
 - Upgrading Contour
 - Enabling TLS between Envoy and Contour
 - Redeploy Envoy
 
Guides
- AWS with NLB
 - Cert-Manager
 - External Authorization
 - JSON logging
 - Migrating to HTTPProxy
 - Prometheus Metrics
 - PROXY Protocol Support
 - 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
Websockets
WebSocket support can be enabled on specific routes using the enableWebsockets field:
# httpproxy-websockets.yaml
apiVersion: projectcontour.io/v1
kind: HTTPProxy
metadata:
  name: chat
  namespace: default
spec:
  virtualhost:
    fqdn: chat.example.com
  routes:
  - services:
    - name: chat-app
      port: 80
  - conditions:
    - prefix: /websocket
    enableWebsockets: true # Setting this to true enables websocket for all paths that match /websocket
    services:
    - name: chat-app
      port: 80
Twitter
Slack