http addon using Ingress, NGINX Ingress Controller and ExternalName Service

[shreya0910]

http addon using Ingress, NGINX Ingress Controller and ExternalName Service

[shreya0910]

Is this standard approach in such scenario when ingress is in application ns?

Yeah, it's a good option indeed

Yes the route is this - ingress -> external name service -> http-add-on service -> interceptor -> you app service -> your app

Your ingress is pointing directly to http-add-on service, which probably isn't correct as you should refer to the external name service

apiVersion: networking.k8s.io/v1
kind: Ingress
...
spec:
  rules:
    - host: test.com
      http:
        paths:
          - backend:
              service:
                name: keda-add-ons-http-interceptor-proxy
                ....

Is that your configuration at ingress level?

Thanks for your inputs. I am closing this issue now.

[JorTurFer]

Hello!
From your manifests, I think that the externalName service is called demo-externalname but the service called from nginx is keda-add-ons-http-interceptor-proxy.
I assume that your ingress is in the application namespace, so the route is

• ingress -> external name service -> http-add-on service -> interceptor -> you app service -> your app
  Try changing the service in the ingress to the externalName service

[JorTurFer]

I can see also an issue related with RBAC in the interceptor, I'd suggest upgrading to v0.7.0. For going live, I'd wait until v0.8.0, because we found an error on helm chart that blocks the helm upgrade, forcing to remove and reinstall (so, for evaluating the add-on can be enough v0.7.0, but for something stable you should wait for v0.8.0)

v0.8.0 will be released soon, and your problem isn't related with the version but with ingress config

[shreya0910]

Hello! From your manifests, I think that the externalName service is called demo-externalname but the service called from nginx is keda-add-ons-http-interceptor-proxy. I assume that your ingress is in the application namespace, so the route is

• ingress -> external name service -> http-add-on service -> interceptor -> you app service -> your app
  Try changing the service in the ingress to the externalName service

Hello!! Sorry that was a typo. I have updated it.
Yes the route is this - ingress -> external name service -> http-add-on service -> interceptor -> you app service -> your app.. Is this standard approach in such scenario when ingress is in application ns? If possible could you share some references. Thanks

[JorTurFer]

Is this standard approach in such scenario when ingress is in application ns?

Yeah, it's a good option indeed

Yes the route is this - ingress -> external name service -> http-add-on service -> interceptor -> you app service -> your app

Your ingress is pointing directly to http-add-on service, which probably isn't correct as you should refer to the external name service

apiVersion: networking.k8s.io/v1
kind: Ingress
...
spec:
  rules:
    - host: test.com
      http:
        paths:
          - backend:
              service:
                name: keda-add-ons-http-interceptor-proxy
                ....

Is that your configuration at ingress level?