-
Notifications
You must be signed in to change notification settings - Fork 502
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
Remove socat and ebtables dependencies from the kubelet package #3722
Conversation
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.
Yes, makes sense to me.
/lgtm |
Signed-off-by: Marko Mudrinić <[email protected]>
/hold cancel |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: saschagrunert, xmudrii 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 |
we should remove these from kubeadm preflight too. similar pr for conntrack, except for these it can be remove without version checks. |
Follow-up on kubernetes/release#3722 Signed-off-by: Sascha Grunert <[email protected]>
Makes sense: kubernetes/kubernetes#127151 |
Follow-up on kubernetes/release#3722 Signed-off-by: Sascha Grunert <[email protected]>
Follow-up on kubernetes/release#3722 Signed-off-by: Sascha Grunert <[email protected]>
Follow-up on kubernetes/release#3722 Signed-off-by: Sascha Grunert <[email protected]>
Follow-up on kubernetes/release#3722 Signed-off-by: Sascha Grunert <[email protected]>
Follow-up on kubernetes/release#3722 Signed-off-by: Sascha Grunert <[email protected]>
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
As per #3707 (comment) and kubernetes/kubernetes#100679, the
socat
dependency is no longer required.As per #3722 (comment), the
ebtables
dependency is no longer required.This PR removes both dependencies from the kubelet package.
Given that this change is in effect since v1.22, I believe it's okay to just remove it from the spec file without adding special cases in
metadata.yaml
.Which issue(s) this PR fixes:
Fixes #3707
Does this PR introduce a user-facing change?
/assign @saschagrunert
cc @kubernetes/release-engineering @aojea
/hold
pending the final confirmation #3707 (comment)