-
Notifications
You must be signed in to change notification settings - Fork 32
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
✨ Switch zap log for global hub agent #1184
Conversation
Signed-off-by: myan <[email protected]>
Signed-off-by: myan <[email protected]>
Signed-off-by: myan <[email protected]>
Signed-off-by: myan <[email protected]>
Signed-off-by: myan <[email protected]>
Signed-off-by: myan <[email protected]>
Signed-off-by: myan <[email protected]>
Signed-off-by: myan <[email protected]>
Signed-off-by: myan <[email protected]>
Signed-off-by: myan <[email protected]>
Signed-off-by: myan <[email protected]>
the environment isn't ready, re run it /test e2e-test |
@yanmxa: The specified target(s) for
Use 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-sigs/prow repository. |
/test test-e2e |
/override ci/prow/sonarcloud |
@yanmxa: Overrode contexts on behalf of yanmxa: ci/prow/sonarcloud 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-sigs/prow repository. |
setup error /test test-e2e |
database isn't ready /test test-e2e |
the kafka cluster is not created /test test-e2e |
Signed-off-by: myan <[email protected]>
|
/override ci/prow/sonarcloud |
@yanmxa: Overrode contexts on behalf of yanmxa: ci/prow/sonarcloud 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-sigs/prow repository. |
enableLocalPolicies: "{{ .EnableLocalPolicies }}" | ||
logLevel: {{.LogLevel}} |
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.
where is LogLevel
from? I do not see any changes in agent controller to set this value.
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.
The LogLevel is from the operator
The agent updates the LogLevel here: https://github.com/stolostron/multicluster-global-hub/pull/1184/files#diff-1f7a85f8429524557f22db6d08a8d0e48634c4073149d0eee6cc9a821d0e7d77R71-R75
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.
Need to have a document about how to change the log level in the runtime environment
Add the document in this pr: #1188 |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: clyang82, yanmxa 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 |
Summary
Related issue(s)
Fixes # #1178, https://issues.redhat.com/browse/ACM-13421
Logger
andSugarLogger
, we also provide thezapr
if you use thelogr
interface.We can see the cloudevents, controller runtime is the same as the format we set. But the lease still uses the klog, which we won't update in this PR. Visit here for more detail about that: kubernetes-sigs/controller-runtime#2656, kubernetes/enhancements#3077
Tests
make unit-tests
.make integration-test
.make e2e-test-all
.