Skip to content
This repository has been archived by the owner on May 22, 2024. It is now read-only.

[BUG] Too long runtime name cause KEDA fail #110

Open
yubingjiaocn opened this issue Mar 27, 2024 · 0 comments
Open

[BUG] Too long runtime name cause KEDA fail #110

yubingjiaocn opened this issue Mar 27, 2024 · 0 comments
Assignees
@yubingjiaocn
Labels
component/cdk Issues related to deployment (CDK or EKS) kind/bug Something isn't working

Comments

@yubingjiaocn
Copy link
Contributor

What happened:
When using a too long runtime name , KEDA scaledObject failed with failed to update ScaledObiect with scaledObjectName label

To Reproduce
Using runtime name longer then 27 characters like dev-sdruntime-h70b2-gif-v02, this will create a dev-sdruntime-h70b2-gif-v02-sd-on-eks-aws-sgs-queue-scaledobject object, which exceed 63-character limit for most Kubernetes resources.

Anything else we need to know?:

Related issue in KEDA: kedacore/keda#2915

Custom HPA name has confirmed not working.

Environment:
@yubingjiaocn yubingjiaocn added kind/bug Something isn't working component/cdk Issues related to deployment (CDK or EKS) labels Mar 27, 2024
@yubingjiaocn yubingjiaocn self-assigned this Mar 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@yubingjiaocn yubingjiaocn

Labels
component/cdk Issues related to deployment (CDK or EKS) kind/bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@yubingjiaocn