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

The add-on isn't the owner of the underlying ScaledObject #703

Closed
JorTurFer opened this issue Jun 15, 2023 · 0 comments · Fixed by #704
Closed

The add-on isn't the owner of the underlying ScaledObject #703

JorTurFer opened this issue Jun 15, 2023 · 0 comments · Fixed by #704
Assignees
Labels
bug Something isn't working

Comments

@JorTurFer
Copy link
Member

Report

We are generating and ScaledObject for KEDA for each HTTPScaledObject, but we aren't setting the owner reference, so the underlying ScaledObject isn't deleted in cascade, with produces delays between both resource deletions.

Expected Behavior

ScaledObject has the owner correctly set and it's removed in cascade when the HTTPScaledObject is deleted

Actual Behavior

ScaledObject hasn't the owner correctly set and it's not removed in cascade when the HTTPScaledObject is deleted

Steps to Reproduce the Problem

Logs from KEDA HTTP operator

example

What version of the KEDA HTTP Add-on are you running?

No response

Kubernetes Version

None

Platform

None

Anything else?

No response

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
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant