-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HPA is not created for deployments with long names (over 53 characters) #704
Comments
The k8s resource's name limit is 253, label has limit 63 chars. Seems like the bug was introduced by this #596, where we put HPA resource name into the label named https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/#labels describes this label as Thanks @aslom, good catch! |
@zroubalik great if the limit can be increased - right now with UUID used in naming Knative Kafka source deployment it allows up to 4 characters to name Kafka source or limit is exceeded :( More details in README in https://github.com/knative/eventing-contrib/pull/886/files |
Yeah, we definitely need to fix this, it will be quite an easy one. |
Fixed |
I would like to reopen this issue as we have to same problem in 2.6.1 version: |
Signed-off-by: Vighnesh Shenoy <[email protected]>
Expected Behavior
Scaling works for deployments with long names.
Actual Behavior
Scaled object name must be very short if deployment name is long (for example when using UUID) as "keda-hpa-" prefix (10 character) is added to deployment name and may exceed 63 characters such as
keda-hpa-kafkasource-knedk1-c28092d0-eb07-4d8d-970c-b21cd3cfe9e8
.HPA is not created:
and scaled object that use deployment with long name
Steps to Reproduce the Problem
kubectl apply -f ../knative-demo-kafka-keda-src1d.yaml
kubectl logs -f -n keda keda-operator-...
Specifications
The text was updated successfully, but these errors were encountered: