-
Notifications
You must be signed in to change notification settings - Fork 90
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
Cannot modify HTTPScaledObjects after moving from 0.7.0 to 0.8.0 #1020
Comments
Same issue here on Kubernetes 1.29. Thanks @jocelynthode , your work around worked just fine. |
f**k I didn't notice that changing the status fields I can break the CRD :/ |
I'm asking because we have to include a check for removing those states from the HTTPScaledObject if they are available |
Yes The upgrade to 0.8.0 was successful and everything seemed to be working. Then when I wanted to edit |
Thanks for the feedback, I'm going to try to fix this during the week and cut a fix release. I thought that old values were dropped automatically but apparently not (every day you learn things xD). The operator will drop them during the upgrade for future releases. Sorry for the inconvenience |
No worries, thanks for the work 🙂 |
just encountered this, bumping so it doesn't get stale:) |
@JorTurFer : Any update on this issue? It's been a few months with no releases. |
Report
After upgrading to 0.8.0. The CRD seems to have changed and the enum for
status.conditions[].type
now only supportsReady
as a value.Before this update to the CRD we supported the following values:
I was able to workaround it by editing the CRD and readding these statuses and then edit them so that the status conditions could be cleaned up.
Expected Behavior
I expect to be able to edit old HTTPScaledObjects
Actual Behavior
Old
HTTPScaledObjects
fail to be edited with the following messages:Steps to Reproduce the Problem
Logs from KEDA HTTP operator
No response
HTTP Add-on Version
0.8.0
Kubernetes Version
1.27
Platform
Other
Anything else?
No response
The text was updated successfully, but these errors were encountered: