Having trouble ScaledObject working for StatefulSet

[rajarshi-chaudhuri]

Hello -

We are using Keda 2.0 - so I'm assuming StatefulSet is supported as per documentation. But I'm having issue with scaling a StatefulSet with Keda. Deployments are working fine.

Any sample with StatefulSet - can you provide?

My scaledobject looks like the following (kubectl describe) -

Name:         gvp-mcp-rcc
Namespace:    gvp
Labels:       app.kubernetes.io/component=shared
              app.kubernetes.io/instance=gvp-mcp-rcc
              app.kubernetes.io/log-monitor-name=gvp-mcp-rcc-log
              app.kubernetes.io/managed-by=Helm
              app.kubernetes.io/name=gvp-mcp
              app.kubernetes.io/part-of=gvp
              app.kubernetes.io/pod-monitor-name=gvp-mcp-rcc-snmp
              app.kubernetes.io/rup-monitor-name=gvp-mcp-rcc-rup-metrics
              app.kubernetes.io/version=v9.0.045.69
              helm.sh/chart=gvp-mcp-9.045.69
              service=gvp
              servicename=gvp-mcp
              tenant=shared
Annotations:  <none>
API Version:  keda.sh/v1alpha1
Kind:         ScaledObject
Metadata:
  Creation Timestamp:  2021-03-10T03:11:45Z
  Generation:          1
  Managed Fields:
    API Version:  keda.sh/v1alpha1
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:labels:
          .:
          f:app.kubernetes.io/component:
          f:app.kubernetes.io/instance:
          f:app.kubernetes.io/log-monitor-name:
          f:app.kubernetes.io/managed-by:
          f:app.kubernetes.io/name:
          f:app.kubernetes.io/part-of:
          f:app.kubernetes.io/pod-monitor-name:
          f:app.kubernetes.io/rup-monitor-name:
          f:app.kubernetes.io/version:
          f:helm.sh/chart:
          f:service:
          f:servicename:
          f:tenant:
      f:spec:
        .:
        f:cooldownPeriod:
        f:maxReplicaCount:
        f:minReplicaCount:
        f:pollingInterval:
        f:scaleTargetRef:
          .:
          f:apiVersion:
          f:kind:
          f:name:
        f:triggers:
    Manager:         Go-http-client
    Operation:       Update
    Time:            2021-03-10T03:11:45Z
  Resource Version:  243684064
  Self Link:         /apis/keda.sh/v1alpha1/namespaces/gvp/scaledobjects/gvp-mcp-rcc
  UID:               c7ba4e98-5b4a-42d4-8c3c-459838390096
Spec:
  Cooldown Period:    3600
  Max Replica Count:  10
  Min Replica Count:  1
  Polling Interval:   15
  Scale Target Ref:
    API Version:  apps/v1
    Kind:         StatefulSet
    Name:         gvp-mcp-rcc
  Triggers:
    Metadata:
      Type:   Utilization
      Value:  10
    Type:     cpu
    Metadata:
      Type:   Utilization
      Value:  30
    Type:     memory
Events:       <none>

Thx
Rajarshi

[zroubalik]

And what problems are you facing? Scaling of StatefulSet should work the same as for Deployment. We have even test for this in our e2e testsuite: https://github.com/kedacore/keda/blob/main/tests/scalers/azure-log-analytics.test.ts#L170-L172

[rajarshi-chaudhuri]

@zroubalik - I see the issue that the scaledobject is getting created fine - but it's not creating a HPA. Not sure what could be the possible cause.

[zroubalik]

Could you please enable DEBUG logging a check KEDA Operator logs?

[zroubalik]

https://github.com/kedacore/keda/blob/main/BUILD.md#setting-log-levels