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 have created a ScaledObject that scales up correctly under certain configurations, but not consistently under all circumstances.
Expected Behavior
I want KEDA to scale my pods to the maximum possible number, or perhaps receive guidance on where my ScaledObject configuration might be incorrect.
Actual Behavior
When minReplicaCount is set to 1 and maxReplicaCount is set to 10, the service starts with 1 pod, and once messages are enqueued to the Kafka topic, the Horizontal Pod Autoscaler (HPA) scales to 3 pods. However, when minReplicaCount is set to 3 and maxReplicaCount is set to 10, the service still starts with 1 pod, but the HPA does not scale.
Scenario:
I have tested this process with a script that injects 1500 messages into the target_topic. I also have a consumer with the consumer group consumer_group that reads from this topic, and after 5 minutes, all messages get consumed. I have verified that the messages are enqueued using Kafka-UI.
Issue with Metrics Visibility
One peculiar issue I've encountered is the inability to check the metric that triggers the scaling. I don't have a way to access this value, which might be part of the problem.
Configurations on my Server
EKS server version: 1.25
KEDA Version: 2.12
Kubecost installed
External metrics config
kubectl get apiservices v1beta1.external.metrics.k8s.io
NAME SERVICE AVAILABLE AGE
v1beta1.external.metrics.k8s.io monitoring/keda-operator-metrics-apiserver True 6h45m
Issue with metrics not visisible
When I attempt to retrieve the metrics that trigger scaling, I don't see any metrics. I should see the KEDA ScaledObject, but it's not there. However, the HPA works correctly for scaling based on these metrics.
If I attempt to retrieve the value for the HPA metrics:
kubectl get --raw "/apis/external.metrics.k8s.io/v1beta1/namespaces/*/s0-kafka-ingress_listing_operations" | jq .
Error from server: scaledObject name is not specified
In my HPA configuration, I can confirm that the metrics are being read and are triggering scaling.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Report
I have created a ScaledObject that scales up correctly under certain configurations, but not consistently under all circumstances.
Expected Behavior
I want KEDA to scale my pods to the maximum possible number, or perhaps receive guidance on where my ScaledObject configuration might be incorrect.
Actual Behavior
When minReplicaCount is set to 1 and maxReplicaCount is set to 10, the service starts with 1 pod, and once messages are enqueued to the Kafka topic, the Horizontal Pod Autoscaler (HPA) scales to 3 pods. However, when minReplicaCount is set to 3 and maxReplicaCount is set to 10, the service still starts with 1 pod, but the HPA does not scale.
Scenario:
I have tested this process with a script that injects 1500 messages into the target_topic. I also have a consumer with the consumer group consumer_group that reads from this topic, and after 5 minutes, all messages get consumed. I have verified that the messages are enqueued using Kafka-UI.
Issue with Metrics Visibility
One peculiar issue I've encountered is the inability to check the metric that triggers the scaling. I don't have a way to access this value, which might be part of the problem.
Configurations on my Server
External metrics config
Issue with metrics not visisible
When I attempt to retrieve the metrics that trigger scaling, I don't see any metrics. I should see the KEDA ScaledObject, but it's not there. However, the HPA works correctly for scaling based on these metrics.
If I attempt to retrieve the value for the HPA metrics:
In my HPA configuration, I can confirm that the metrics are being read and are triggering scaling.
Current objects
ScaledObject Configuration:
HPA Configuration
Keda Operator Logs
I have reviewed the KEDA Operator logs, and there doesn't seem to be any apparent issues.
Any insights or assistance in resolving this issue would be greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions