-
Notifications
You must be signed in to change notification settings - Fork 596
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
[Charts] Add logVerbosityLevel variable to all Helm charts #1679
Conversation
#1654 ? |
not sure the lint issue is related? |
@jichenjc it is, no? I haven't incremented chart versions, and it's complaining about it. |
@gman0 yes,so please update the version :) |
@jichenjc ok I thought it was a pipeline bug that it was still asking for version bump. |
Should be ok now. All jobs passed. |
I've updated the release note so that it mentions new variable in helm chart values. |
thanks ~ |
Any updates on this pls? @ramineni ? |
charts/cinder-csi-plugin/values.yaml
Outdated
# Log verbosity level. | ||
# See https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/logging.md | ||
# for description of individual verbosity levels. | ||
logVerbosityLevel: 0 |
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.
if nothing is passed in argument , isnt default log level would be 2?
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.
@ramineni do you have some reference for this where it says it really defaults to 2? If not I'll go check it myself later today or in the coming days.
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.
Because AFAIK it indeed defaults to zero:
-v=0
Enable V-leveled logging at the specified level.
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.
But that's just what I implied when I saw -v=0
. I couldn't find anything explicitly stating what's the default level though, so that's why I'm asking if you saw it somewhere else.
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.
Some more references:
Whether an individual call to V generates a log record depends on the setting of the -v and --vmodule flags; both are off by default.
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.
@gman0 Its there in same link you have mentioned in comment above :)
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.
If that's the case, I think it's sensible to set all logVerbosityLevel
values to 2
. What do you and others think?
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.
Yeah, I agree
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.
@ramineni I think https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/logging.md just summarizes the recommendations rather than actual defaults that klog is configured with. Either way I'll set the level to 2 as we just agreed.
@gman0 @jichenjc Yes, according to this ,#1654 , we have decided not to bump version as it causes confusion . We need to fix that not to cause error if there is no version bump. |
This is weird, according to https://github.com/helm/chart-testing/blob/main/doc/ct_lint.md, the job shouldn't check chart version. |
/override openstack-cloud-keystone-authentication-authorization-test |
@ramineni: Overrode contexts on behalf of ramineni: openstack-cloud-keystone-authentication-authorization-test In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Will do, @lingxiankong. Maybe we can get your fix merged and then I'll rebase this PR? |
its merged |
c8b7ac7
to
495b441
Compare
All CI jobs passed. PTAL again. |
@@ -27,6 +27,7 @@ spec: | |||
image: "{{ .Values.csi.attacher.image.repository }}:{{ .Values.csi.attacher.image.tag }}" | |||
imagePullPolicy: {{ .Values.csi.attacher.image.pullPolicy }} | |||
args: | |||
- "-v={{ .Values.logVerbosityLevel }}" |
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.
it should be --v= .. right? does one dash also work?
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.
@ramineni both forms are allowed.
$ ./openstack-cloud-controller-manager --help
...
-v, --v Level
number for the log level verbosity
$ ./cinder-csi-plugin --help
...
-v, --v Level number for the log level verbosity
$ ./manila-csi-plugin --help
...
-v, --v Level number for the log level verbosity
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.
Usually single-character flags are denoted with a single dash.
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.
ok thanks, then should be ok
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.
one comment inline, else looks good
/lgtm |
/approve Thanks! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lingxiankong The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…s#1679) * added logVerbosityLevel variable to all Helm charts * set logVerbosityLevel to 2
What this PR does / why we need it:
This PR adds
logVerbosityLevel
variable to all Helm charts in this repository. Operators can now choose how verbose they want their logs. Default levels are set to 2.Which issue this PR fixes(if applicable):
fixes #
Special notes for reviewers:
Release note: