Autoscale https upstream service

[cary205]

Hello,

I have deployed a deployment which I want to autoscale.
The deployment exposes port with https.
Is http-add-on supports https upstream service?

Thanks

[tomkerkhove]

Yes, it should. Did you encounter issues?

[nkuzman]

Hi @tomkerkhove ,

I'm not sure if I have the same issue as @cary205 there, but I also encountered a problem with HTTPS port.

So, an application exposes HTTPS port only and is exposed to public via ingress (nginx) which has SSL passthrough enabled (certificate is served by microservice itself, not by ingress).

HTTP add-on is installed in a separate namespace from application itself, so I use an ExternalName service to route requests to interceptor.
The problem is that as soon as I switch ingress to point to ExternalName service instead of application's service, HTTPS requests start to fail, and application can be accessed only via HTTP, which triggers scaler, but requests obviously fail with bad gateway error.

Ingress setup:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    nginx.ingress.kubernetes.io/ssl-passthrough: "true"
  name: myapp
spec:
  ingressClassName: nginx
  rules:
  - host: myhost.com
    http:
      paths:
      - backend:
          service:
            name: externalname-service
            port:
              number: 8080
        path: /
        pathType: Prefix

ExternalName service:

apiVersion: v1
kind: Service
metadata:
  name: externalname-service
spec:
  externalName: keda-add-ons-http-interceptor-proxy.keda.svc.cluster.local
  type: ExternalName

Application service:

apiVersion: v1
kind: Service
metadata:
  name: myapp-service
spec:
  ports:
  - name: https
    port: 8443
    protocol: TCP
    targetPort: https
  type: ClusterIP

HTTPScaledObject:

kind: HTTPScaledObject
apiVersion: http.keda.sh/v1alpha1
metadata:
    name: myapp-scaler
spec:
    hosts:
        - "myhost.com"
    targetPendingRequests: 1
    scaleTargetRef:
        deployment: myapp
        service: myapp-service
        port: 8443

Add-on was installed using default settings (interceptor proxy listens on 8080).

It there a misconfiguration somewhere or am I missing some additional setup which is required for this scenario?
Please let me know if you need some additional info.

Thank you.

[gshhong]

I also encountered the same problem.
I am not sure if the latest version 0.8.0 has solved this problem.