-
Notifications
You must be signed in to change notification settings - Fork 692
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
Rebase k8s dependencies to 1.19-rc.2 #337
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: damemi 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 |
/retest |
Weird that these checks are failing CI, they pass locally for me and I'm running go 1.14.4 (same as the prow job image. Tested in a container:
And I do get some error with golangci-lintbut the vendor should verify and the tests should pass... |
I think it's some assumption we're making in our script that's messed up... I can sometimes get it to reproduce the failure by switching to master and running verify-vendor, but then running update-vendor fixes it (and produces no noticeable code changes) |
Ok I can consistently reproduce this by switching between
I can go back and forth with this pattern forever, but it seems like It seems to be something about |
The problem is only related to OpenAPIV2 packages, related to the lowercasing of the new imports (see kubernetes/client-go#741 and the linked kube-openapi PR in that issue). This would explain why the diff doesn't show up in git
which carries over when switching to the newer branch, so that's why I could switch between them and reproduce the issue. The |
Need to make changes to update our policy conversion since default conversions no longer take place in 1.19 after kubernetes/kubernetes#90018 |
@seanmalloy @ingvagabund I just updated this PR to 1.19-rc2. If we want to merge this to get our master branch up to a "pre-release" state I'm ok with it, that will let us make sure our other ongoing changes right now will work with 1.19 and lets us update our CI as well. Then the eventual bump to GA 1.19 should just be smooth. What do you think? |
@@ -35,12 +33,6 @@ const GroupName = "descheduler" | |||
// SchemeGroupVersion is group version used to register these objects | |||
var SchemeGroupVersion = schema.GroupVersion{Group: GroupName, Version: runtime.APIVersionInternal} | |||
|
|||
func init() { | |||
if err := addKnownTypes(scheme.Scheme); err != nil { |
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 looks like the addKnownTypes
function(lines 46 to 51) is no longer called. So should the addKnownTypes
function just be removed from this file too?
I also noticed that some other files have their own addKnownTypes
functions, so maybe these should be cleaned up too?
if err := addKnownTypes(scheme.Scheme); err != nil { - pkg/apis/componentconfig/v1alpha1/register.go
localSchemeBuilder.Register(addKnownTypes, addDefaultingFuncs)
I'm honestly not sure if these need to be cleaned up or not, but just wanted to point this out just in case.
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.
Good point, let me check these out. I think at least some of them can be removed if not all
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.
This addKnownTypes
is still used by the SchemeBuilder
: https://github.com/kubernetes-sigs/descheduler/blob/72946602bbc51c3aee3fe438120040a04e53cbdb/pkg/api/register.go#L25f0456cede4d61f48e51015136685ba1dR25
The others in ComponentConfig aren't called, but I think I need to update those to manually invoke AddToScheme
like I did here
Sounds good. As long as release-1.19 branch is cut after GA 1.19 rebase. |
Yeah that would be exactly the plan, to not cut release-1.19 until after 1.19 GA |
/lgtm @damemi these changes look good tome. Please remove the hold when you are ready for this to merge. |
This will be troublesome every time someone runs /lgtm |
This shouldn't be a problem once it's fixed here. It's really only a problem for case-insensitive filesystems (like Mac) which don't see the filename change when the version was bumped (and so, don't commit the change). For that same reason, if anyone else is on a Mac they shouldn't see any change running go.mod, so nothing to worry about there. Just a hitch but from this version on it should be good |
CI looks good, so I'll release the hold. Planned 1.19 GA is August 25, so this will give us some good soak time to catch any bugs (like #353, which this fixes so that's another reason to get it in sooner). Thanks @seanmalloy and @ingvagabund |
Rebase k8s dependencies to 1.19-rc.2
This is an in-place PR to start updating our deps to 1.19 for the upcoming 1.19 k8s release
Fixes #353