keda

KEDA is an event-based autoscaler for workloads on Kubernetes, allowing fine-grained autoscaling including to and from zero for event driven Kubernetes workloads. The KEDA Helm chart automates deployment and configuration of KEDA in Kubernetes clusters using Minimus images.

Prerequisites

A subscription to the Minimus images included in the chart
A running Kubernetes cluster (v1.23 or higher is recommended)
kubectl installed and configured
Helm v3.8 or higher for OCI support (Installation instructions)
Cluster Admin privileges

Note: KEDA installs Custom Resource Definitions (CRDs) for ScaledObjects, ScaledJobs, and TriggerAuthentications. Ensure the installing user has cluster-admin privileges.

Try It Out

In this example we will deploy KEDA on a Kubernetes cluster using the Minimus KEDA Helm chart. KEDA will provide event-driven autoscaling for your Kubernetes workloads.

Step 1: Start Cluster

If you have a cluster to work with, skip this step. Otherwise, start a Minikube cluster. Deployment instructions

Step 2: Create Namespace

Create a namespace:

kubectl create ns keda

Step 3: Deploy the Helm Chart

Deploy the Minimus Helm chart:

helm install my-keda oci://helm.mini.dev/keda \
  --version 2.19.0 \
  -n keda \
  --wait

If you want to override the chart's defaults, go to the Values tab, save a copy locally with your changes. Deploy the chart with your overrides using -f values.yaml:

helm install my-keda oci://helm.mini.dev/keda \
  --version 2.19.0 \
  -f values.yaml \
  -n keda \
  --wait

Step 4: Verify KEDA is Running

Confirm the chart deployed successfully and KEDA started:

kubectl get pods -n keda

You should see output similar to:

NAME                                                      READY   STATUS    RESTARTS   AGE
my-keda-keda-admission-webhooks-xxxxxxxxx-xxxxx           1/1     Running   0          2m
my-keda-keda-operator-xxxxxxxxx-xxxxx                     1/1     Running   0          2m
my-keda-keda-operator-metrics-apiserver-xxxxxxxxx-xxxxx   1/1     Running   0          2m

Step 5: Test Event-Driven Autoscaling

Create a sample deployment to use as a scale target:

kubectl create deployment sample-app --image=nginx --replicas=1 -n keda

Create a ScaledObject to test KEDA's event-driven autoscaling:

cat <<EOF | kubectl apply -f -
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
  name: sample-scaledobject
  namespace: keda
spec:
  scaleTargetRef:
    name: sample-app
  minReplicaCount: 1
  maxReplicaCount: 5
  triggers:
    - type: cron
      metadata:
        timezone: Etc/UTC
        start: "0 0 * * *"
        end: "0 23 * * *"
        desiredReplicas: "2"
EOF

Verify the ScaledObject was created and is ready:

kubectl get scaledobject -n keda

You should see output similar to:

NAME                  SCALETARGETKIND      SCALETARGETNAME   MIN   MAX   READY   ACTIVE    AGE
sample-scaledobject   apps/v1.Deployment   sample-app        1     5     True    Unknown   30s

Step 6: Clean Up

Uninstall the chart and delete the namespace to remove all resources:

helm uninstall my-keda -n keda
kubectl delete namespace keda

Terms & Info

Trademark

This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.

Disclaimer

Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.

This page is available on desktop