Common Issues

Diagnosing and resolving common issues you might encounter with Kedify and KEDA.

Unknown scaler type `kedify-http` or `kedify-envoy-http`

If you deployed a ScaledObject with the trigger kedify-http or kedify-envoy-http and the ScaledObject is not ready, you might encounter one of the following error messages in the KEDA Operator logs:

no scaler found for type: kedify-http
no scaler found for type: kedify-envoy-http

This indicates that you are using an unsupported KEDA distribution. These scalers (HTTP and Envoy HTTP) are supported only with the Kedify build of KEDA.

You need to uninstall your current KEDA distribution and ensure you are using Managed mode during the Kedify installation.

Kedify Agent is unable to connect to the Kedify service

The Kedify Agent connects using gRPC over port 443. Check to make sure port 443 is open and you are able to make outbound network connections.

Command not found: `kubectl`

You will need to install kubectl before proceeding. Here are some examples using common package managers, depending on your platform:

Homebrew (macOS and Linux)

brew install kubectl

Apt (Debian/Ubuntu)

sudo apt-get update && sudo apt-get install -y kubectl

Yum (CentOS/RHEL/Fedora)

sudo yum install -y kubectl

Chocolatey (Windows)

choco install kubernetes-cli

Custom DNS Domain

If your Kubernetes cluster uses a custom DNS domain instead of the standard cluster.local suffix, you need to properly configure your setup.

Istio Integration

When setting up Kedify, you might encounter an error like (v1beta1.external.metrics.k8s.io) status FailedDiscoveryCheck if you have Istio installed on the cluster.

To mitigate this problem, please follow this guide.