-
Notifications
You must be signed in to change notification settings - Fork 3.4k
chore(hubble-ui): Silence access log produced by readinessProbe #38725
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
chore(hubble-ui): Silence access log produced by readinessProbe #38725
Conversation
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.
LGTM. At first I was concerned that disabling access log based on user agent could be a security issue, but that doesn't apply to the api, so I think this should be fine.
I'd still like to have a review from the Hubble UI team, though.
Looks good to me. I've tagged this with |
/test |
Hey @geakstr , did you get a chance to review this change? Does it make sense to you? |
FWIW the ci-ginkgo failures look like a particular failure in the |
e4ae8ef
to
44f4e1c
Compare
/test |
Signed-off-by: Marco Maurer <mkilchhofer@users.noreply.github.com>
44f4e1c
to
d871c65
Compare
/test |
Please ensure your pull request adheres to the following guidelines:
description and a
Fixes: #XXX
line if the commit addresses a particularGitHub issue.
Fixes: <commit-id>
tag, thenplease add the commit author[s] as reviewer[s] to this issue.
This is a little follow-up of my contribution ~2years ago:
Without this change, you see a lot of those lines inside the log:
With the change, these lines will not appear since we silence them based on the kubelet's User-Agent.
Release note entry: