Kedify Agent and data collection
The Agent connects a Kubernetes cluster to the Kedify service through an outbound authenticated gRPC connection. It manages enabled KEDA and HTTP Scaler releases, HTTP traffic autowiring, and collection of component and selected workload metrics.
Install one Agent per connected cluster using Helm. Optional capabilities, including KPA and Insights, have separate enablement and collection settings.
Configuration
Section titled “Configuration”Use Helm values for enablement paths, environment mappings and chart defaults; use KedifyConfiguration for installation resource fields. Select compatible releases before enabling an optional controller.
Container Metrics for Resource Recommendations
Section titled “Container Metrics for Resource Recommendations”The Agent reads selected container utilization from the Kubernetes Metrics API and sends it for recommendation processing. Label-gated namespaces and explicit namespace overrides determine collection scope. Follow Insights settings to enable, verify or stop collection; this does not enable PRA or PRP automatically.
API Key
Section titled “API Key”The Agent uses a credential to authenticate its outbound service connection. Obtain and store it through the Helm installation credential flow and your approved secret owner. Base64 is encoding, not encryption; do not paste real keys into documentation or shared diagnostics. Access, telemetry and connectivity boundaries explains the trust/data responsibilities.
For signal-to-workload inspection, use Workload diagnostics.