Networking & Connectivity

This section covers how to expose the Traceable Platform and route external traffic to it across different Kubernetes distributions and ingress technologies.

Overview

The platform supports two routing modes — legacy (NGINX Ingress routing directly to services) and envoy (a single traceable-router Service fronted by any controller or cloud load balancer). The right choice depends on your cluster and the ingress technology available in your environment.

In This Section

• Connecting to the Traceable Platform
• Legacy (NGINX) vs Envoy routing modes
• The traceable-router component (listeners, ports, TLS)
• Cloud Kubernetes via Service type LoadBalancer (EKS/GKE/AKS)
• NGINX, Traefik, OpenShift Route options
• TLS termination strategies and a decision matrix

• Validation and troubleshooting

• Migrating from NGINX Ingress

• Kurl-based (VM) — Option A: Traefik ingress controller + Envoy mode
• Kurl-based (VM) — Option B: traceable-router as a DaemonSet (no separate ingress controller)
• Cloud platform migration: LoadBalancer + Envoy mode
• Uninstalling NGINX (self-managed and Traceable-managed)
• Post-migration checklist and troubleshooting

Quick Decision Guide

Your environment	Recommended option
Managed cloud (EKS / GKE / AKS)	Direct LoadBalancer Service on traceable-router
ingress-nginx installed (cluster scope)	NGINX legacy mode
Red Hat OpenShift	OpenShift Route (Envoy mode)
Traefik	Envoy mode with the matching controller

See Connecting to the Traceable Platform for full configuration details.

Related Sections

• Platform-Specific Guides
• Prerequisites: TLS Certificates
• Operations: Update DNS

Support

For networking assistance, contact support@harness.io.