-
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
Add documentation for replacing existing HPA with an Scaled Object without deleting the existing resource #4066
Comments
Actually maybe need simple example with deployment in k8s - needed to delete hpa section? needed to delete replica count or not? |
Transferring to core repo as this might be a feature we can introduce. If not, then we should provide better docs |
@ksemele , |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to inactivity. |
This feels relevant, by using |
Currently, there isn't any way to do it because the validation webhook will block the ScaledObject if it's already managed by another ScaledObject or HPA, so you can't deploy a ScaledObject for a workload already monitored by another HPA. |
@JorTurFer Something like: advanced.takeOverExistingHPA = true |
I think that it's something doable and it could enable migration scenarios 😄 Could you open another issue to track the new feature? |
Yes, thx!! |
Done: #4457 |
Use-Case
In a company where most of the services already have HPA, it would be ideal to have a backward compatible transition to ScaledObjects where it would take over the existing HPA, while the user would only need to delete the HPA yaml file (not using git ops).
The text was updated successfully, but these errors were encountered: