Define KEDA readiness and liveness probes

[zroubalik]

KEDA should report it state/availability to the kubernetes cluster.

[tomkerkhove]

Duplicate of #237?

[zroubalik]

@tomkerkhove no, these are probes for the KEDA Operator deployment, to expose KEDA state to the cluster. #237 is talking about probes on the target deployment and scaling based on the probes there.

[tomkerkhove]

Oh I've missed that, fully agree on this one then!

[zroubalik]

Fixed in #792

[tomkerkhove]

Can we get some docs on this on https://keda.sh/docs/2.0/operate/?

[zroubalik]

I am not sure this is something worth documenting. Those probes exposes state of the Operator and Metrics Server Deployment toward kubernetes, eg. kubernetes scheduler knows when the Deployment is not available and should try to spin another pod.

[tomkerkhove]

Let's close since it's part of our YAML & chart?

[hila3000]

@zroubalik @tomkerkhove Where can I see the Yamls and Chart? I want to see examples of liveness/readiness configuration.

[tomkerkhove]

Chart can be found here: https://github.com/kedacore/charts/tree/master/keda

[hila3000]

@tomkerkhove I don't see there an example for scaledobject.yaml.

This is what I have from version 1.5.0. Should it tweaked to be compatible with v2.0.0?

apiVersion: keda.k8s.io/v1alpha1
kind: ScaledObject
metadata:
  name: lf-scaledobject-{{ .Values.tenantId }}
  namespace: {{ .Values.lf_namespace }}
  labels:
    deploymentName: log-forwarding-{{ .Values.tenantId }}
spec:
  scaleTargetRef:
    deploymentName: log-forwarding-{{ .Values.tenantId }}
  pollingInterval: 180
  cooldownPeriod:  43200
  minReplicaCount: 0
  maxReplicaCount: 5
  triggers:
  - type: gcp-pubsub
    metadata:
      subscriptionSize: "50"
      subscriptionName: "lf-data-{{ .Values.tenantId }}-sub"
      credentials: GENERIC_GOOGLE_CREDENTIALS

[tomkerkhove]

The probes are for KEDA runtime, ScaledObject scales your workload, so you are in control of those probes.

[tomkerkhove]

Or maybe I'm not fully getting your question.

[zroubalik]

You can refer Migration Guide https://keda.sh/docs/2.0/migration/

[hila3000]

Exactly what I needed :) Thanks!