# Install with Helm

Install the Kedify Agent, KEDA and HTTP Scaler in one Helm release. For an existing upstream KEDA installation, start with [migration](https://docs.kedify.io/troubleshooting/migration-from-keda/).

## Prerequisites

- A Kubernetes cluster, an authorized `kubectl` context and Helm.

- A [Kedify account](https://dashboard.kedify.io/api/auth/login) and the organization credentials below.

- Reviewed [Versions](https://docs.kedify.io/getting-started/versions/), [component sizing](https://docs.kedify.io/concepts/resource-footprint/) and [networking requirements](https://docs.kedify.io/installation/networking/).

## Get the command from the Dashboard

In Overview or Clusters, select **Connect Cluster → Helm Installation**. The dialog provides the installation steps. For manual setup, obtain the credentials below.

 ![Kedify Dashboard Helm installation dialog](https://docs.kedify.io/assets/images/installation/kedify-helm-installation-dialog.png) 

## Prepare Installation

Follow these steps to install Kedify using Helm manually.

### Getting Organization ID

In the Kedify dashboard, navigate to `Organization` and select [Details](https://dashboard.kedify.io/organization-details). Copy the `ID`.

Alternatively, if you already have an existing installation, you can read the `Organization ID` using:

```bash
kubectl set env -nkeda deployment/kedify-agent --list | grep KEDIFY_ORGANIZATION_ID
```

### Getting API Key

If you already have a [Kedify Agent](https://docs.kedify.io/concepts/kedify-agent/) deployed, you can retrieve your pre-provisioned API key from a `Secret` in the same Kubernetes cluster:

```bash
kubectl get secret -n keda kedify-agent -o=jsonpath='{.data.apikey}' | base64 --decode
```

If you don't have an existing Agent, you can generate a new API Key in the Kedify dashboard. Navigate to `Organization` and select [API Keys](https://dashboard.kedify.io/api-keys). Click `Create Agent Key` and copy the key.

Keep Agent API keys in your approved secret store. Update installations that use a key before revoking it.

## Install

These commands explicitly enable KEDA and HTTP Scaler in the Agent chart. All charts are available in the [Kedify charts repository](https://github.com/kedify/charts).

### Kedify Helm Repository

To install Kedify using Helm, you first need to add the Kedify Helm repository to your local Helm configuration.

```bash
helm repo add kedifykeda https://kedify.github.io/charts
helm repo update kedifykeda
```

### Quick Installation

Replace `clusterName`, `$YOUR_ORG_ID` and `$YOUR_API_KEY` with your installation values.

This command installs the Kedify Agent along with KEDA and the [Kedify HTTP Scaler](https://docs.kedify.io/scalers/http-scaler/). If you don't want to install KEDA or the HTTP Scaler, you can disable them by setting `keda.enabled=false` or `keda-add-ons-http.enabled=false`.

You can also install additional components such as the [OTel Scaler](https://docs.kedify.io/scalers/otel-scaler/) and [Kedify Predictor](https://docs.kedify.io/scalers/predictive-scaler/). You can enable them by setting `otel-add-on.enabled=true` or `kedify-predictor.enabled=true` respectively.

```bash
helm upgrade --install kedify-agent kedifykeda/kedify-agent \
--namespace keda \
--create-namespace \
--version v0.8.0 \
--set clusterName="my-cluster" \
--set agent.orgId="$YOUR_ORG_ID" \
--set agent.apiKey="$YOUR_API_KEY" \
--set keda.enabled=true \
--set keda-add-ons-http.enabled=true \
--set otel-add-on.enabled=false \
--set kedify-predictor.enabled=false
```

## Verify the installation

```bash
kubectl get pods -n keda
kubectl get apiservice v1beta1.external.metrics.k8s.io
```

Confirm the enabled components are ready and the external metrics API reports `AVAILABLE=True`. Check the cluster connection in the [Dashboard](https://docs.kedify.io/concepts/kedify-dashboard/), then configure a [scaler](https://docs.kedify.io/features/) and verify workload behavior. [Autoscaling Checks](https://docs.kedify.io/features/autoscaling-checks/) can exercise the signal-to-replica path.

## Other installation paths

- [Separate component releases](https://docs.kedify.io/installation/components/)

- [Argo CD](https://docs.kedify.io/installation/argo-cd/)

- [Terraform](https://docs.kedify.io/installation/terraform/)

- [ARM nodes](https://docs.kedify.io/installation/arm/)

- [Custom DNS and Istio](https://docs.kedify.io/installation/cluster-configuration/)

- [Multi-tenant installation](https://docs.kedify.io/how-to/multitenant-scaling/)

- [Private registry](https://docs.kedify.io/installation/air-gapped/)

## Configuration reference

[Helm values](https://docs.kedify.io/reference/helm-values/) · [Capability enablement](https://docs.kedify.io/reference/capability-availability/) · [KedifyConfiguration](https://docs.kedify.io/reference/kubernetes-api/kedifyconfiguration/) · [Access and data boundaries](https://docs.kedify.io/security-and-compliance/access-and-data/)

---
Canonical: https://docs.kedify.io/installation/helm/
Source: src/pages/installation/helm.astro
Documentation index: https://docs.kedify.io/llms.txt