-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
⚠ Bump to k8s.io/* v0.33.0-alpha.1 #3104
base: main
Are you sure you want to change the base?
Conversation
@@ -1819,7 +1819,7 @@ var _ = Describe("manger.Manager", func() { | |||
<-m.Elected() | |||
|
|||
Eventually(func() *corev1.Event { | |||
evts, err := clientset.CoreV1().Events("").Search(m.GetScheme(), &ns) | |||
evts, err := clientset.CoreV1().Events("").SearchWithContext(ctx, m.GetScheme(), &ns) |
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.
fyi. This was not a breaking change in client-go. Search is just deprecated in favor of SearchWithContext
@@ -109,6 +110,10 @@ func (f *FakeInformer) Run(<-chan struct{}) { | |||
f.RunCount++ | |||
} | |||
|
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 SharedIndexInformer interface has new additional methods. So I extended the FakeInformer accordingly.
This was expected and previously discussed in kubernetes/kubernetes#126387 (comment)
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.
In general there should be some follow-up to leverage changes like kubernetes/kubernetes#127709 & kubernetes/kubernetes#126387
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.
You can use the "trick" from kubernetes/kubernetes#126379 with 's;// *Contextual logging: ;//logcheck:context //;'
in your vendor directory, then run logcheck
to get errors about using functions which have better alternatives.
We haven't sketched out a timeline yet, but for 1.33 I am hoping to adapt source code. Then in 1.34, those free-form comments could become proper logcheck:context
tags and thus active for users of logcheck.
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.
Thx!
/assign @alvaroaleman @vincepri (cc @pohly just fyi, I think everything as expected so far) |
LGTM label has been added. Git tree hash: 130eabcc979cf864fe69f6cb18e5aa9608e9c547
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alvaroaleman, sbueringer 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 |
/hold |
Signed-off-by: Stefan Büringer [email protected]