Skip to content
Docs

Kedify Agent

The Kedify Agent is responsible for establishing a secure connection between your Kubernetes cluster and the Kedify platform. It handles the installation and lifecycle management of KEDA and the HTTP Scaler on your clusters, providing robust scaling capabilities and telemetry insights. The Kedify Agent can manage a large number of installations across multiple clusters using secure gRPC connections to communicate with the Kedify Dashboard, ensuring the seamless collection and display of telemetry data.

Key functionalities of the Kedify Agent include:

  • Installation Management: The agent manages the installation and versioning of KEDA and the HTTP Scaler using the Helm package manager. It ensures that the correct versions of these components are deployed and maintained across your clusters.

  • Telemetry Collection: The agent includes a telemetry collector that scrapes metrics from both KEDA and the HTTP Scaler. This telemetry data provides users with valuable insights into their configurations and scaling behaviors, which are displayed in the Kedify Dashboard.

  • Secure Communication: The Kedify Agent establishes a secure, outbound gRPC connection to the Kedify Service, ensuring that all data transmitted between your clusters and the Kedify platform is secure.

  • Custom Resource Management: The agent manages Kedify custom resources, providing autowiring and comprehensive management of the HTTP Scaler. For more information on custom resources, refer to the Kedify Custom Resource Definitions.

The Kedify Agent is installed and configured using a single, unique kubectl apply command generated and provided by Kedify via the dashboard. This command sets up the agent with all necessary configurations to connect to the Kedify platform and manage your KEDA and HTTP Scaler installations efficiently.

The Kedify Agent relies on the Helm package manager to manage and install versioned KEDA images.

Environment Variables

The Kedify Agent Deployment supports several environment variables that can be configured to customize its behavior:

  • HTTP_HEALTHCHECK_DEBOUNCER_SECONDS: The default value is 5. This variable sets the fallback mechanism for HTTP Scaler Traffic Autowiring. For more details, see the HTTP Scaler Traffic Autowiring documentation.

  • KEDIFY_PROXY_SELF_HEALING: The default value is true. By default, agent tries to re-deploy the kedify-proxy if it went down. However this functionality can be turned off by setting this to false. Then if one deletes the deployment, scales the proxy to zero replicas, breaks its service, or make any other similar action that will lead to an unavailable kedify-proxy endpoints, agent will rewire the communication back to the original target, but will not try to recover from the issue.

  • NO_COLOR: If set to true Kedify agent’s log will not contain the ANSI escape characters that make the log colorful. By default the logs has colors.

  • NO_BANNER: If set to true Kedify agent’s log will not print the ASCI logo of kedify. By default the logo is printed.