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

Bug: Check for "none" when checking pod identity provider #4748

Merged
merged 1 commit into from
Jun 29, 2023

Conversation

joelsmith
Copy link
Contributor

The prometheus scaler should expect a value of "none" to determine
that no pod identity provider is set.

Checklist

Fixes #4695

The prometheus scaler should expect a value of "none" to determine
that no pod identity provider is set.

Signed-off-by: Joel Smith <joelsmith@redhat.com>
@joelsmith joelsmith requested a review from a team as a code owner June 28, 2023 19:12
@github-actions
Copy link

Thank you for your contribution! 🙏 We will review your PR as soon as possible.

While you are waiting, make sure to:

Learn more about:

@joelsmith
Copy link
Contributor Author

@zroubalik PTAL. Thanks!

@JorTurFer
Copy link
Member

JorTurFer commented Jun 29, 2023

/run-e2e prometheus
Update: You can check the progress here

@JorTurFer JorTurFer mentioned this pull request Jun 29, 2023
13 tasks
@JorTurFer
Copy link
Member

Thanks for the fix @joelsmith <3
Checking the change, it should happen on any instance of KEDA, but I couldn't reproduce it using latest core (and I tried with exactly the same values as the user). Is there any change in OpenShift code at some point?

@JorTurFer JorTurFer enabled auto-merge (squash) June 29, 2023 08:40
@JorTurFer JorTurFer merged commit a9af2b5 into kedacore:main Jun 29, 2023
JorTurFer pushed a commit to JorTurFer/keda that referenced this pull request Jun 29, 2023
JorTurFer pushed a commit to JorTurFer/keda that referenced this pull request Jun 29, 2023
)

Signed-off-by: Jorge Turrado <jorge.turrado@scrm.lidl>
JorTurFer pushed a commit to JorTurFer/keda that referenced this pull request Jun 29, 2023
)

Signed-off-by: Jorge Turrado <jorge.turrado@scrm.lidl>
@joelsmith
Copy link
Contributor Author

I could only reproduce that error if I included this stanza:

spec:
  podIdentity: 
    provider: none

which the reporter mentioned as something they once tried. I did run into an issue where a change to the trigger auth object didn't cause the scaled object to re-reconcile, so adding or removing that stanza didn't have any effect unless the scaled object was created after the trigger auth. So my best guess is that the reporter's logs came from a time where the initial trigger auth had the stanza when the scaled object was created. In other words, while I think this is a good fix, I am guessing that there is more to the problem the reporter was having and this is more of a side issue, not the actual issue causing it to fail. Hopefully I am wrong and the new version with the fix starts working for them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ScaledObject with Camel K Integration custom resource is broken
2 participants