Hide the annoying logs coming from client-go ("the server could not find the requested resource") #639
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
maelvls force-pushed the VC-33564-hide-spurious-log-lines branch from e30960b to 08bd016 Compare maelvls changed the title maelvls changed the title maelvls force-pushed the VC-33564-hide-spurious-log-lines branch 2 times, most recently from 08bd016 to 24d6b92 Compare 
maelvls commented Mar 14, 2025
go.mod Outdated
| go 1.22.0 | ||
| go 1.23.0 | ||
| | ||
| toolchain go1.23.4 |
There was a problem hiding this comment.
The toolchain stanza kept re-appearing after running go mod tidy.
With the vendored version of Go, though, it wouldn't appear:
$ make vendor-go $ _bin/tools/go version go version go1.23.4 darwin/arm64 $ make go-tidyThe change we are trying to get is: kubernetes/kubernetes#126387
…ync" This commit groups the log messages about the datagatherers not being able to be synced, and also makes the log message less alarming.
maelvls force-pushed the VC-33564-hide-spurious-log-lines branch from 24d6b92 to ae44ffc Compare 
SgtCoDFish approved these changes Mar 14, 2025
Good point... I don't know if it makes it better or not, but controller-runtime's latest release uses v0.33.0-alpha.3... 😅 |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Ref: VC-33564
Thanks to the change made in client-go (kubernetes/kubernetes#126387) which was released in v0.33.0-alpha.1, we can now hide most of the annoying logs "the server could not find the requested resource" that we are seeing coming from client-go (as Richard started doing in #624). These messages are now gone:
I propose that we also group and rephrase the "Failed to complete initial sync" messages. Instead of:
I propose this:
You will still see the permissions errors if the RBAC rules are configured properly:
Before:
After:
Manual Testing
There is no automated test for this change. Thus, I went ahead and manually tested the feature.
I've used the tenant https://ven-tlspk.venafi.cloud/. To access the API key, use the user
system.admin@tlspk.qa.venafi.ioand the password is visible in the page Production Accounts (private to Venafi). Then go to the settings and find the API key.export APIKEY=...Create the Private Key JWT:
Build image and chart:
Then, install the chart:
See that the annoying logs aren't shown anymore: