Install components separately
Install KEDA, HTTP Scaler, Agent, OTel and Predictor as separate Helm releases. Use this path when each component has its own values and release lifecycle. For the bundled installation, use Helm.
The following components can be installed and configured separately:
- Kedify Agent - The main Kedify component (Documentation)
- KEDA - The Kedify build of KEDA (Documentation)
- HTTP Scaler - HTTP-based autoscaler (Documentation)
- OTel Scaler - OpenTelemetry-based general purpose autoscaler (Documentation)
- Kedify Predictor - Predictive autoscaler (Documentation)
0. Prerequisites
Before proceeding, ensure you have added the Kedify Helm repository to your local Helm configuration as described in the Kedify Helm Repository section.
1. Configure Kedify build of KEDA
Create a values_keda.yaml file with the following content. See all available options in the values.yaml file.
image: keda: tag: v2.20.2-0 registry: ghcr.io repository: kedify/keda-operator metricsApiServer: tag: v2.20.2-0 registry: ghcr.io repository: kedify/keda-metrics-apiserver webhooks: tag: v2.20.2-0 registry: ghcr.io repository: kedify/keda-admission-webhooksprometheus: operator: enabled: true metricServer: enabled: true webhooks: enabled: truewatchNamespace: ''rbac: scaledRefKinds: - apiGroup: '*' kind: '*'
## Please fill this file with your custom values based on the available options2. Configure HTTP Scaler
Create a values_http.yaml file with the following content. See all available options in the values.yaml file.
images: tag: v0.11.1-6 operator: ghcr.io/kedify/http-add-on-operator interceptor: ghcr.io/kedify/http-add-on-interceptor scaler: ghcr.io/kedify/http-add-on-scalerinterceptor: replicas: min: 1 resources: requests: cpu: '0.1' memory: 32Mi limits: cpu: 1 memory: 64Miscaler: replicas: 1 resources: requests: cpu: '0.1' memory: 16Mi limits: cpu: 0.5 memory: 64Mioperator: replicas: 0
## Please fill this file with your custom values based on the available options3. Configure Kedify Agent
Disable bundled subcharts in this release because the commands below install them separately.
Create a values_kedify.yaml file with the following content. See all available options in the values.yaml file.
keda: enabled: falsekeda-add-ons-http: enabled: falseotel-add-on: enabled: falsekedify-predictor: enabled: falseclusterName: my-clusteragent: orgId: "YOUR_ORG_ID" apiKey: "YOUR_API_KEY" image: tag: v0.7.1 repository: ghcr.io/kedify/agent
## Please fill this file with your custom values based on the available options4. Install Kedify
To install Kedify using the custom values files, run the following commands:
helm upgrade --install keda kedifykeda/keda --namespace keda \ --version=v2.20.2-0 \ --create-namespace \ --values values_keda.yaml
helm upgrade --install keda-add-ons-http kedifykeda/keda-add-ons-http \ --version=v0.11.1-6 \ --namespace keda \ --values values_http.yaml
helm upgrade --install kedify-agent kedifykeda/kedify-agent \ --version=v0.7.1 \ --namespace keda \ --values values_kedify.yaml5. (Optional) Install OTel Scaler
Prepare a values_otel.yaml file with the following content. See all available options in the values.yaml file.
image: repository: ghcr.io/kedify/otel-add-on tag: v0.1.4## Please fill this file with your custom values based on the available optionsThen, install the OTel Scaler using the following command:
helm upgrade --install kedify-otel-scaler oci://ghcr.io/kedify/charts/otel-add-on \ --version=v0.1.4 \ --namespace keda \ --values values_otel.yaml6. (Optional) Install Kedify Predictor
Prepare a values_predictor.yaml file with the following example content. To see all the available options, check the default values.yaml file.
settings: logs: logLvl: infokedaPredictionController: retrainUsingJobs: false## Please fill this file with your custom values based on the available optionsThen, install the Kedify Predictor using the following command:
helm upgrade --install kedify-predictor oci://ghcr.io/kedify/charts/kedify-predictor \ --version=v0.1.6 \ --namespace keda \ --values values_predictor.yamlVerify
Run the installation checks, then configure a scaler. Consult Helm values for additional fields.