Skip to content
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

Removing a deployment doesn't get rid of autoscale rules #80

Closed
jeffhollan opened this issue Apr 16, 2019 · 5 comments · Fixed by #81
Closed

Removing a deployment doesn't get rid of autoscale rules #80

jeffhollan opened this issue Apr 16, 2019 · 5 comments · Fixed by #81
Labels
bug Something isn't working

Comments

@jeffhollan
Copy link
Member

When I delete a deployment to Kore I still see the horizontalpodautoscaler.autoscaling resource floating around. Ideally that would be removed after I remove a deployment

@jeffhollan
Copy link
Member Author

@Aarthisk any thoughts on this?

@ahmelsayed
Copy link
Contributor

you'll need to delete the scaledObject I think. We don't track deployments, only scaled objects.

@jeffhollan
Copy link
Member Author

ah yes - fair point. Same thing may stand though. Removing the ScaledObject also doesn't seem to get rid of the autoscaling

@ahmelsayed ahmelsayed added the bug Something isn't working label Apr 16, 2019
ahmelsayed added a commit that referenced this issue Apr 16, 2019
@ahmelsayed
Copy link
Contributor

yep, that's definitely a bug, the controller wasn't calling deleted on the handler when a scaledObject is deleted. I opened a PR

@ahmelsayed
Copy link
Contributor

restart your kore deployment and you should get the new one.

patnaikshekhar pushed a commit to patnaikshekhar/keda that referenced this issue Jul 17, 2019
Aarthisk pushed a commit that referenced this issue Aug 12, 2019
preflightsiren pushed a commit to preflightsiren/keda that referenced this issue Nov 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants