-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
Migrate k8s.io/csi-translation-lib/.* to structured logging #124439
Migrate k8s.io/csi-translation-lib/.* to structured logging #124439
Conversation
Skipping CI for Draft Pull Request. |
5a57d18
to
5814951
Compare
@@ -602,7 +609,8 @@ func TestEphemeralVolumeOwnerCheck(t *testing.T) { | |||
|
|||
podName := util.GetUniquePodName(pod) | |||
|
|||
dswp.findAndAddNewPods() | |||
_, ctx := ktesting.NewTestContext(t) |
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.
Hi @pohly , Can you take a look? NewTestContext(t)
and Init(t)
, which is preferred?
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.
Init
is simpler and thus preferred.
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.
Just beware that it cannot be used in staging (yet) - I first need to move k/k/test/utils/ktesting into a staging repo.
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.
@carlory @pohly Thank you for your comments.
I first need to move k/k/test/utils/ktesting into a staging repo.
Regarding this, is there anything I can help with, such as creating issues for repository creation at https://github.com/kubernetes/org?
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.
I first need to polish it a bit more and gather more experience with it before proposing it for staging.
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.
Understood. I'll switch to using Init(t)
from k/k/test/utils/ktesting
for testing, excluding staging.
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.
I changed to use Init(t)
instead of NewTestContext(t)
.
aa67f41
/sig instrumentation |
/test pull-kubernetes-e2e-capz-windows-master |
Flakying test: #125903 |
We've made an update that should resolve that test |
All the test passed but one which is tracked in #126180 due to a new feature that got turned on today |
c70a10c
to
1298c8a
Compare
CAPZ tests should be fixed now. If not, this should fix them: kubernetes/test-infra#33022 /retest |
/test pull-kubernetes-e2e-capz-windows-master |
1 similar comment
/test pull-kubernetes-e2e-capz-windows-master |
/lgtm |
LGTM label has been added. Git tree hash: 39465816fd0090e3e4df09e56ceba13877a10cbd
|
/test pull-kubernetes-e2e-capz-windows-master |
/approve |
/assign @SergeyKanzhelev For SIG Node approval. |
Maybe add a release note here? |
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
/approve
kubelet change looks ok
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bells17, jsafrane, pohly, SergeyKanzhelev, yangjunmyfm192085 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 |
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Migrate to use structured logging and contextual logging in csi-translation-lib.
https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/migration-to-structured-logging.md
I've implemented it to use contextual logging, as csi-translation-lib is a library and applications using csi-translation-lib may utilize contextual logging.
kubernetes-csi/csi-lib-utils#149 (review)
The csi-translation-lib is used in the kubernetes-csi/external-provisioner, and this modification is necessary to enable contextual logging within the kubernetes-csi/external-provisioner
based PR: #120640
Which issue(s) this PR fixes:
Fixes #120639
Special notes for your reviewer:
Does this PR introduce a user-facing change?