-
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
Bug: Check for "none" when checking pod identity provider #4748
Conversation
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>
Thank you for your contribution! 🙏 We will review your PR as soon as possible. While you are waiting, make sure to:
Learn more about: |
@zroubalik PTAL. Thanks! |
/run-e2e prometheus |
Thanks for the fix @joelsmith <3 |
I could only reproduce that error if I included this stanza:
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. |
The prometheus scaler should expect a value of "none" to determine
that no pod identity provider is set.
Checklist
Fixes #4695