namespacedNameError on Proxy when attempting to submit a cURL call to it

Report

The Keda http proxy is unable to find hosts and returns NamespacedName is nil error

Expected Behavior

When the proxy is hit with an appropriate host it should be able to serve traffic without an error

Actual Behavior

When I portforward the http-add-on proxy and hit it with a cURL call, it returns Not Found and the following can be seen on the keda-add-ons-http-interceptor-proxy logs:

RROR    LoggingMiddleware.RoutingMiddleware.StaticHandler    Not Found    {"routingKey": "//myhost.com/", "namespacedNameError": "PANIC=value method k8s.io/apimachinery/pkg/types.NamespacedName.MarshalLog called using nil *NamespacedName pointer", "stream": "<nil>"}
github.com/kedacore/http-add-on/interceptor/handler.(*Static).ServeHTTP
    github.com/kedacore/http-add-on/interceptor/handler/static.go:36
github.com/kedacore/http-add-on/interceptor/middleware.(*Routing).ServeHTTP
    github.com/kedacore/http-add-on/interceptor/middleware/routing.go:49
github.com/kedacore/http-add-on/interceptor/middleware.(*Logging).ServeHTTP
    github.com/kedacore/http-add-on/interceptor/middleware/logging.go:42
github.com/kedacore/http-add-on/interceptor/middleware.(*Metrics).ServeHTTP
    github.com/kedacore/http-add-on/interceptor/middleware/metrics.go:24
net/http.serverHandler.ServeHTTP
    net/http/server.go:3137
net/http.(*conn).serve
    net/http/server.go:2039

Steps to Reproduce the Problem

Attempt to deploy the example helm chart
Port forward the proxy to 8080:8080 as the walkthrough suggests with kubectl port-forward svc/keda-add-ons-http-interceptor-proxy -n keda 8080:8080
Run the following cURL call: curl -H "Host:myhost.com" 127.0.0.1:8080

Logs from KEDA HTTP operator

N/A, no relevant HTTP operator logs

HTTP Add-on Version

0.8.0

Kubernetes Version

1.28

Platform

Amazon Web Services

Anything else?

Keda is installed in the keda namespace along with the http-add-on:

Nevermind, this wasn't the case. Not sure what the specific issues was here but I've got a good feeling I just made a spelling mistake somewhere and when I re-applied things they fixed themselves. Regardless I spent some time going down a rabbit hole. Couple of learnings for anybody who might stumble on this:

DNS may have trouble resolving for the externalName service, always try out the FQDN (i.e. keda-add-ons-http-interceptor-proxy.keda.svc.cluster.local) before trying much else.

You may have to define ports in the externalName service as well:

apiVersion: v1
kind: Service
metadata:
name: my-proxy
spec:
type: ExternalName
externalName: keda-add-ons-http-interceptor-proxy.keda.svc.cluster.local
ports:
- port: 80
targetPort: 8080

The ALB Ingress Controller does not play nice with the externalName service as of now either, but there is an open PR as of writing this. To get around it, I unfortunately just have to run keda and the http add on in each of my namespaces.

kedacore / http-add-on