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

Restart of keda-operator causes ScaledJob object to be updated #5656

Open
chinmaygopal opened this issue Apr 2, 2024 · 2 comments · May be fixed by #5876
Open

Restart of keda-operator causes ScaledJob object to be updated #5656

chinmaygopal opened this issue Apr 2, 2024 · 2 comments · May be fixed by #5876
Labels
bug Something isn't working

Comments

@chinmaygopal
Copy link

chinmaygopal commented Apr 2, 2024

Report

Restart/Recreation of keda-operator causes ScaledJob object to be updated, which leads to Jobs being rolled out as per the RolloutStrategy.

Expected Behavior

Restart/Recreation of the keda-operator should not update the ScaledJob object

Actual Behavior

Restart/Recreation of the keda-operator somehow update the ScaledJob object leading to Jobs being rolled out as per the RolloutStrategy.

Steps to Reproduce the Problem

  1. Kill the keda-operator (with replicas >1).
  2. Wait for the keda-operator to be recreated.
  3. In the Kubernetes events for the ScaledJob object, around the time the keda-operator was restarted the following events can be seen:
    i. KEDAJobsCreated
    ii. KEDAScalersStarted

KEDA Version

2.13.1

Kubernetes Version

1.27

Platform

Microsoft Azure

Scaler Details

No response

Anything else?

This could also be the expected behavior of the keda-operator. However I do not understand why any changes the to keda-operator should affect the ScaledJob object.

@chinmaygopal chinmaygopal added the bug Something isn't working label Apr 2, 2024
@JorTurFer
Copy link
Member

Hello,
This is weird and it shouldn't happen. Are you willing to take a look and open a PR with the fix?

Copy link

stale bot commented Jun 7, 2024

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.

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Jun 7, 2024
@zroubalik zroubalik removed the stale All issues that are marked as stale due to inactivity label Jun 7, 2024
@josefkarasek josefkarasek linked a pull request Jun 10, 2024 that will close this issue
7 tasks
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: To Triage
Development

Successfully merging a pull request may close this issue.

3 participants