Contour does not natively support OCSP stapling. This is a deliberate design choice, and there are currently no plans to implement this feature ( Support OCSP Stapling · Issue #4683 · projectcontour/contour)
Recommended Architecture:
Because traffic in most Tanzu/Contour environments is routed through a load balancer (such as VMware AVI/NSX ALB or F5), the most robust way to implement OCSP stapling is at the ingress load balancer layer.
- Do not attempt configuration in Contour/Envoy: There are no configuration parameters in the Contour ConfigMap or HTTPProxy CRDs to enable this.
- Configure at the Load Balancer: Implement OCSP stapling on your front-end Load Balancer (e.g., AVI/F5). The Load Balancer is responsible for TLS termination and can be configured to cache and staple OCSP responses.
- Maintain Trust: Ensure the Load Balancer trusts the certificate presented by the Envoy pods, and the Envoy pods trust the certificates from the backend applications. No special configuration is required on the Contour side.
Reference for AVI LB:
https://techdocs.broadcom.com/us/en/vmware-security-load-balancing/avi-load-balancer/avi-load-balancer/32-1/vmware-avi-load-balancer-configuration-guide/security/ocsp-stapling-in-nsx-advanced-load-balancer.html
Reference for F5 Load balancer:
https://docs.cloud.f5.com/docs-v2/multi-cloud-app-connect/how-to/adv-security/configure-ocsp