-
Notifications
You must be signed in to change notification settings - Fork 26
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
General cleanup and updating dependencies #231
Conversation
detiber
commented
Mar 2, 2022
•
edited
edited
- Update go version to v1.17
- Update alpine to v3.15
- Update packngo to v0.22.0
- Update k8s dependencies to v0.23.4
- Cleanup unused code, constants, and variables
- fix some lint related issues
- Update error wrapping to use go v1.13+ style error wrapping instead of github.com/pkg/errors
Signed-off-by: Jason DeTiberus <detiber@users.noreply.github.com>
Signed-off-by: Jason DeTiberus <detiber@users.noreply.github.com>
Signed-off-by: Jason DeTiberus <detiber@users.noreply.github.com>
These are the cleanup changes from #230 |
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 looks great. I had 2 questions, but I would not block on them.
k8s.io/component-base v0.21.2 | ||
k8s.io/klog/v2 v2.8.0 | ||
k8s.io/api v0.23.4 | ||
k8s.io/apimachinery v0.23.4 |
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.
Does this create any backwards-compatibility issues with older cluster versions? Or do we just say, "use this version x of CCM for version y of cluster"?
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 shouldn't cause any issues, since client-go has a pretty good track record of backward/forward compatibility
) | ||
|
||
require ( | ||
github.com/Azure/go-ansiterm v0.0.0-20210617225240-d185dfc1b5a1 // indirect |
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.
That's quite the growth in explicit requirements. Why is that?
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's new behavior in go 1.17 related to how go builds up the dependency graphs for projects: https://go.dev/doc/go1.17#go-command
Testing all was clean. Thanks for the cleanup @detiber |