# Capability availability and enablement

Availability depends on the installed component set and enabled capabilities. A chart flag, a controller, a telemetry path and a hosted feature are different prerequisites. Independent latest tags on the [versions page](https://docs.kedify.io/getting-started/versions/) do not establish a tested bundle.

## Capability prerequisites and enablement

| Area | Required component or evidence | Enable/configure owner |
| --- | --- | --- |
| Event-driven replicas/jobs | KEDA and the selected source/authentication path | [Built-in scalers](https://docs.kedify.io/scalers/keda-scalers/) |
| HTTP and zero activation | Kedify KEDA, HTTP components, Agent/proxy integration and working route | [HTTP scaling](https://docs.kedify.io/scalers/http-scaler/) |
| Existing Envoy metrics | Compatible Kedify trigger and configured metrics sink; no zero activation | [Existing Envoy](https://docs.kedify.io/scalers/http-envoy-scaler/) |
| OTel metrics | OTel add-on and selected export/collector pipeline | [OTel setup](https://docs.kedify.io/how-to/otel-scaler-integrations/) |
| PRP | Agent PRP controller, target opt-in where configured, in-place resize support | [PRP enablement](https://docs.kedify.io/features/pod-resource-profiles/) |
| PRA | Agent PRA controller, metric/resize permissions and supported resize | [PRA enablement](https://docs.kedify.io/features/pod-resource-autoscaler/#enablement-and-pod-opt-in) |
| Insights | Connected Agent; Agent v0.7.0 or later; selected namespace utilization and Metrics API | [Insights settings](https://docs.kedify.io/features/insights/) |
| FinOps | Collected capacity plus provider/pricing metadata for spend estimates | [FinOps interpretation](https://docs.kedify.io/features/finops/) |
| Prediction | Predictor/controller, history store and useful training data | [Predictor enablement](https://docs.kedify.io/how-to/predictive-scaler-installation/) |
| Fleet visibility | Separate connected installation identity per cluster | [Cluster connection](https://docs.kedify.io/concepts/kedify-dashboard/) |
| Distributed replicas/jobs | Agent distributed controllers, registered member access; jobs also need KEDA raw metrics | [Distributed scaling](https://docs.kedify.io/features/multi-cluster-scaling/) |
| vCluster | Supported central/virtual topology and API discovery/access | [vCluster procedure](https://docs.kedify.io/how-to/vcluster-scaling/) |
| Tenant KEDA/KPA | Compatible paired releases, non-overlapping namespace scope and shared CRD ownership | [Tenant installation](https://docs.kedify.io/how-to/multitenant-scaling/) |
| ScalingPolicy / timed resume | Applicable Agent controllers and target ownership | [Policy](https://docs.kedify.io/features/scaling-policy/) · [Maintenance](https://docs.kedify.io/features/resume-scaling/) |
| ScalingGroup | Kedify KEDA group controller; documented HPA/metric restrictions | [Scaling Groups](https://docs.kedify.io/features/scaling-groups/) |
| ScaleAdapter / node buffers | Enabled adapter, target permissions and provider-specific capacity support | [Custom targets](https://docs.kedify.io/features/scale-adapter/) · [Node capacity](https://docs.kedify.io/capabilities/node-capacity/) |
| Inference | Documented routing/InferencePool or vLLM metric scenario, model readiness and device capacity | [HTTP inference setup](https://docs.kedify.io/scalers/http-scaler-for-inference/) |
| Health checks, HTTP logs and traces | Their emitting components and configured collection path | [Observation](https://docs.kedify.io/troubleshooting/workload-scaling/) |
| Private registry | Mirrored release images, pull credentials and applicable service connectivity | [Private registry install](https://docs.kedify.io/installation/air-gapped/) |
| Security evidence | Applicable image/host/deployment scope and release evidence | [Security and compliance](https://docs.kedify.io/security-and-compliance/) |

## Version and default provenance

[Helm values](https://docs.kedify.io/reference/helm-values/) records chart-scoped defaults from the inspected Agent v0.7.0 snapshot and preserves newer documented feature paths separately. Collection flags do not install KPA or every monitored component. KPA’s current documentation scopes Kubernetes support to 1.33–1.35; verify the paired KEDA/Agent/KPA bundle before rollout. In-place resize requirements apply independently of the Agent chart’s broad Kubernetes install constraint.

Use `kubectl get crd <crd-name> -o yaml` to compare the installed fields with the [API reference](https://docs.kedify.io/concepts/kedify-custom-resource-definitions/). A CRD being present does not prove its controller is enabled or owns the target namespace.

## Before enabling a capability

Record installed versions and the configuration owner, verify the linked prerequisites, then enable one bounded workload and inspect its expected outcome. Confirm support and account availability for the intended component combination with your release/installation owner before production changes. Use [Kedify capabilities](https://docs.kedify.io/features/) to select a benefit rather than enabling flags merely because they exist.

Last updated: Sep 21, 2026

---
Canonical: https://docs.kedify.io/reference/capability-availability/
Source: src/content/docs/reference/capability-availability.md
Documentation index: https://docs.kedify.io/llms.txt