I'm running the latest K3S, MetalLB, and Traefik 2.5 on Fedora 35 Server. I installed K3S without Traefik and the built-in load balancer. Installing the MetalLB and Traefik projects was easy. I'm also running Cert-Manager and I've generated a signed SSL certificate for the Traefik dashboard. All of that works.
My problem? Routing Ingress or IngressRoute traffic from trafik to another namespace kubernetes endpoint. Traefik is able to build the route from the IngressRoute to the endpoint. I can see it in the dashboard. But when I attempt to execute a curl command using the deployed application's DNS namd i.e. apache.apps.example.com, I get "Bad Gateway." I've increased Traefik logging to Deubg, and I'm getting a 502 no route to host error message. My assumption is this: A kuberntes policy is blocking the traffic between namespaces. Either it has to do with the kubernetes service and endpoint's port, which is usually 80, or there is a missing network rule, a CRD, or something else. I shelled into the traefik pod and curl to the endpoint or service ClusterIP address generates the same error message.
My question is: What else should I be logging? I think there is something that I'm overlooking due to my newness to Kubernetes itself.