-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Remove non fatal errors from SPIRE client in operator #28698
Conversation
50439b7
to
fd4f338
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice @meyskens
Only one non-blocking nit in a comment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your PR!
I've left a couple of questions inline.
This pull request has been automatically marked as stale because it |
fd4f338
to
3675e57
Compare
/test |
This removed level=error errors from the spire-client system in the operator. As it is expected to fail on initial startup of SPIRE to have connection issues Cilium will retry. Some errors also came from the SPIFFE library itself which is why a wrapper to log them as warnings instead was added. Signed-off-by: Maartje Eyskens <maartje.eyskens@isovalent.com>
075399d
to
3b2b3d0
Compare
/test |
@meyskens can all open conversations be considered resolved? |
@dylandreimerink judging from the thumbs ups i think they can |
Regarding my comments everything is fine, I marked them as resolved. 👍 |
This removed level=error errors from the spire-client system in the operator. As it is expected to fail on initial startup of SPIRE to have connection issues Cilium will retry.
Some errors also came from the SPIFFE library itself which is why a wrapper to log them as warnings instead was added.
Fixes: #27842