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

pkg/nodediscovery: Updates updateCiliumNodeResource() Warning Message #30257

Merged
merged 1 commit into from Jan 18, 2024

Conversation

danehans
Copy link
Contributor

Previously, updateCiliumNodeResource() would emit a warning message whenever the k8s client could not get the local CiliumNode resource from the k8s api server. This caused the following benign log message for new installations since the CiliumNode resource has yet to be created:

level=warning msg="Unable to get node resource" error="ciliumnodes.cilium.io \"kind-control-plane\" not found" subsys=nodediscovery

This PR updates updateCiliumNodeResource() to only generate the warning message when the maximum number of attempts has been reached.

Fixes: #29330

Previously, updateCiliumNodeResource() would emit a warning message whenever the k8s
client could not get the local CiliumNode resource from the k8s api server. This caused
the following benign log message for new installations since the CiliumNode resource has
yet to be created:

`level=warning msg="Unable to get node resource" error="ciliumnodes.cilium.io \"kind-control-plane\" not found" subsys=nodediscovery`

This PR updates updateCiliumNodeResource() to only generate the warning message when the
maximum number of attempts has been reached.

Fixes: cilium#29330

Signed-off-by: Daneyon Hansen <daneyon.hansen@solo.io>
@danehans danehans requested a review from a team as a code owner January 16, 2024 02:44
@maintainer-s-little-helper maintainer-s-little-helper bot added the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Jan 16, 2024
@joestringer joestringer added the needs-backport/1.15 This PR / issue needs backporting to the v1.15 branch label Jan 16, 2024
@maintainer-s-little-helper maintainer-s-little-helper bot added this to Needs backport from main in v1.15.0-rc.1 Jan 16, 2024
@joestringer joestringer added release-note/bug This PR fixes an issue in a previous release of Cilium. release-blocker/1.15 This issue will prevent the release of the next version of Cilium. labels Jan 16, 2024
@maintainer-s-little-helper maintainer-s-little-helper bot removed dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. labels Jan 16, 2024
Copy link
Contributor

@ldelossa ldelossa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall this looks good to me.

A bit curious if we should still log the 'attempts' with a better message like "CiliumNode resources not ready: trying %d more times" or something like this.

That maybe too much non-actionable info tho.

@ldelossa
Copy link
Contributor

/test

@maintainer-s-little-helper maintainer-s-little-helper bot added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Jan 17, 2024
@danehans
Copy link
Contributor Author

A bit curious if we should still log the 'attempts' with a better message like "CiliumNode resources not ready: trying %d more times" or something like this.

@ldelossa thanks for the review! I have no objection to adding an info-level log message similar to what you suggest if others agree.

@ldelossa
Copy link
Contributor

@danehans - Lets merge this in right no since it's a release blocker. We can add the extra logging in a subsequent PR.

@ldelossa ldelossa added this pull request to the merge queue Jan 18, 2024
Merged via the queue into cilium:main with commit aef0523 Jan 18, 2024
63 checks passed
@danehans danehans deleted the issue_29330 branch January 18, 2024 17:00
@giorio94 giorio94 mentioned this pull request Jan 22, 2024
12 tasks
@giorio94 giorio94 added backport-pending/1.15 The backport for Cilium 1.15.x for this PR is in progress. and removed needs-backport/1.15 This PR / issue needs backporting to the v1.15 branch labels Jan 22, 2024
@maintainer-s-little-helper maintainer-s-little-helper bot moved this from Needs backport from main to Backport pending to v1.15 in v1.15.0-rc.1 Jan 22, 2024
@giorio94 giorio94 added backport-done/1.15 The backport for Cilium 1.15.x for this PR is done. and removed backport-pending/1.15 The backport for Cilium 1.15.x for this PR is in progress. labels Jan 29, 2024
@maintainer-s-little-helper maintainer-s-little-helper bot moved this from Backport pending to v1.15 to Backport done to v1.15 in v1.15.0-rc.1 Jan 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-done/1.15 The backport for Cilium 1.15.x for this PR is done. ready-to-merge This PR has passed all tests and received consensus from code owners to merge. release-blocker/1.15 This issue will prevent the release of the next version of Cilium. release-note/bug This PR fixes an issue in a previous release of Cilium.
Projects
No open projects
v1.15.0-rc.1
Backport done to v1.15
Development

Successfully merging this pull request may close these issues.

GKE: Warning Unable to get node resource
4 participants