-
Notifications
You must be signed in to change notification settings - Fork 105
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
dependency: update k8s component dependency to v0.27.1
#244
dependency: update k8s component dependency to v0.27.1
#244
Conversation
a163ad9
to
d5fe8e5
Compare
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: harshanarayana, vladimirvivien 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 |
@harshanarayana some of my CI tests are failing trying to upgrade K8s deps to |
@embano1 I believe that can be done.. @vladimirvivien @cpanato what do you think? May be we set a cadence for this with every k8s release like descheduler has been doing lately? |
Wonder if it needs to be minor or patch semantic version release? |
@embano1 I believe we could setup a cadence for once every minor release change. Release for patch version based mechanism could be need only. Until we get the release out though, you can still use the main branch with commit based vendoring/requirements to get the new changes into your workflow. |
Yeah, I know. But I don't want to manually change this since everything is driven by dependabot using semver |
Uptick the dependencies for
v0.27.1
and also address the changes required to handle #243Takes care of the Deprecation done to the
wait
package helpers via kubernetes/apimachinery@831cf05Closes #243