Autoscale HTTP applications on Kubernetes with KEDA and Kedify
Introduction
Install Kedify using Helm
Install an ingress controller for testing HTTP autoscaling
Deploy an HTTP application through Kubernetes Ingress
Configure and test HTTP autoscaling with Kedify
Next Steps

  Log an issue

  Fork and edit

  Discuss on Discord

About this Learning Path

Skill level:  Introductory
Reading time:  45 min
Last updated:  06 Oct 2026
Skill level:
  Introductory
Reading time:
  45 min
Last updated:
  06 Oct 2026
Author:Zbynek Roubalik, Kedify
Arm IP:Neoverse
Tags: Containers and Virtualization AWS Graviton Microsoft Azure Cobalt Google Axion Linux Kubernetes Helm KEDA Kedify
Author:
  • Zbynek Roubalik, Kedify
Arm IP:
Neoverse
Tags:
Containers and Virtualization AWS Graviton Microsoft Azure Cobalt Google Axion Linux Kubernetes Helm KEDA Kedify

Who is this for?

This is an introductory topic for developers running HTTP workloads on Kubernetes who want to enable event-driven autoscaling with KEDA and Kedify.

What will you learn?

Upon completion of this Learning Path, you will be able to:

  • Install Kedify (KEDA build, HTTP Scaler, and Kedify Agent) with Helm.
  • Verify that Kedify and KEDA components are running in the cluster.
  • Deploy a sample HTTP application and test autoscaling behavior.

Prerequisites

Before starting, you will need the following:

  • A running Kubernetes cluster (local or cloud)
  • Kubectl and Helm installed
  • Access to the Kedify Service dashboard to obtain your Organization ID and API key (sign up at Kedify dashboard )

Summary

AI-assisted

This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
You’ll enable event-driven HTTP autoscaling on an Arm-based Kubernetes cluster with KEDA and Kedify. First, you’ll install the required Kedify charts, verify their components, and configure Traefik as an ingress controller on arm64 nodes. Then, you’ll deploy a web service and expose it through ingress. You’ll create a scaled object, generate traffic, and observe scale-out, scale-in, and scale-to-zero behavior.

Frequently asked questions

AI-assisted

These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
How do I verify that Kedify and KEDA installed correctly?
Run kubectl get pods -n keda and confirm that the KEDA, HTTP scaler, and Kedify Agent pods show 1/1 in READY and Running in STATUS before continuing.
Do I need to install Traefik if my cluster already has an ingress controller?
No. If your cluster already has an ingress controller, skip the Traefik installation and use its endpoint and IngressClass name while deploying the application.
Which deployment target should I use for the ingress controller on Arm-based nodes?
Install Traefik with Helm and set its node selector and toleration for arm64 nodes to run the controller on Arm nodes in your cluster.
What do I need to connect the cluster to Kedify’s cloud service?
Use your Organization ID and API key from the Kedify Service dashboard. Provide these values when installing the Kedify Agent to establish the connection.
How do I know autoscaling is working after deploying the sample app?
Generate HTTP load against the application’s ingress and watch the service scale out. When load stops, it should scale back in, including scale-to-zero when idle.
Next