You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to propose a new feature and a breaking change to improve the autoscaling capabilities of the OpenTelemetry Collector Helm chart.
Add KEDA support:
KEDA (Kubernetes Event-driven Autoscaling) reached General Availability in August 2023, and its ecosystem is growing rapidly. Given its importance in the Kubernetes autoscaling landscape, I believe it's crucial to add support for KEDA in our Collector's Helm chart.
Restructure autoscaling configuration:
To accommodate both HPA (Horizontal Pod Autoscaler) and KEDA, I propose a breaking change in the autoscaling configuration. This change will provide a clear separation between the two autoscaling methods and improve the overall structure of the configuration.
Proposed changes:
a. Move autoscaling.behavior to autoscaling.hpa.behavior
b. Introduce an autoscaling.mode field to select between hpa (default) and keda
c. Create a new configuration section autoscaling.keda to support KEDA-specific settings
Hi guys,
I would like to propose a new feature and a breaking change to improve the autoscaling capabilities of the OpenTelemetry Collector Helm chart.
Add KEDA support:
KEDA (Kubernetes Event-driven Autoscaling) reached General Availability in August 2023, and its ecosystem is growing rapidly. Given its importance in the Kubernetes autoscaling landscape, I believe it's crucial to add support for KEDA in our Collector's Helm chart.
Restructure autoscaling configuration:
To accommodate both HPA (Horizontal Pod Autoscaler) and KEDA, I propose a breaking change in the autoscaling configuration. This change will provide a clear separation between the two autoscaling methods and improve the overall structure of the configuration.
Proposed changes:
a. Move
autoscaling.behavior
toautoscaling.hpa.behavior
b. Introduce an
autoscaling.mode
field to select betweenhpa
(default) andkeda
c. Create a new configuration section
autoscaling.keda
to support KEDA-specific settingsExample of the proposed structure:
Originally posted by @matheus-meneses in #1475
The text was updated successfully, but these errors were encountered: