@pedror17109482  only a year late, but hopefully this is still of use to you:

⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.

Based on my research into Pega's Kubernetes deployment documentation and available resources, I can confirm that Pega Platform deployments are compatible with Contour as a Kubernetes ingress controller. Pega's official documentation states that its platform deployments are designed to work with "the load balancing tools featured in the Kubernetes environment of the deployment," which means Contour is a supported option.

Key points regarding Pega's load balancer support:

1. Flexible Load Balancer Configuration: Pega Platform is designed to work with various Kubernetes ingress controllers and load balancers, including Contour.
2. Architecture Compatibility: As noted in the Pega deployment architecture documentation, "A load balancer or Kubernetes ingress connects to the exposed Pega nodes to allow user access to the cluster." Contour, being a standard Kubernetes ingress controller, meets this architectural requirement.
3. TLS Support Consideration: If you plan to implement TLS between the load balancer/ingress and pods, Pega supports mounting and passing TLS certificates into containers. This is particularly relevant given your previous certificate issues with Traefik.
4. Contour's Features: Contour is an Envoy-based ingress controller that provides a control plane for the Envoy edge and service proxy. It's designed for dynamic configuration updates without requiring load balancer restarts, which could help avoid the certificate refresh issues you've encountered.

Since you've already verified that Contour meets the minimum requirements specified in Pega's documentation, you should be well-positioned to implement this solution in your environment.

References:
Understanding the Pega deployment architecture
Containerized deployments in Kubernetes environments
Contour Project Website