-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Missing kernel modules for kube-proxy's IPVS mode #3087
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
I can confirm this still happens in minikube v0.33.1, and would be happy to review any PR's which fix this issue. Following the repro instructions:
|
I can confirm the same. Building the kernel and configuring shows a few more changes, but other than that, after re-building the ISO then IPVS works. Also
|
Thanks! I'd be happy to accept any PR's which update the ISO appropriately. |
Hi @tstromberg , I've created a PR to resolve this here: #3783 |
Closing, as v1.0.0 includes #3783 to address this. |
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
FEATURE REQUEST
Please provide the following details:
Environment:
minikube version: v0.28.2
OS: MacOS 10.13
VM driver: xhyve
ISO version: ~/.minikube/cache/iso/minikube-v0.28.1.iso
What happened:
kube-proxy won't start in ipvs mode
What you expected to happen:
kube-proxy should start in ipvs mode
How to reproduce it (as minimally and precisely as possible):
After minikube boots, set
mode: "ipvs"
inconfig.conf
inkube-proxy
ConfigMap:To apply new configuration, delete the old pod and k8s will create a new one,
as required by corresponding DaemonSet:
$ kc get -n kube-system pods NAME READY STATUS RESTARTS AGE ... kube-proxy-49psk 1/1 Running 0 11h ... $ kc delete -n kube-system po/kube-proxy-49psk pod "kube-proxy-49psk" deleted $ kc get -n kube-system pods NAME READY STATUS RESTARTS AGE ... kube-proxy-x7qgq 1/1 Running 0 7m ...
Output of
minikube logs
(if applicable):Anything else do we need to know:
With all ipset-related modules, kube-proxy starts as expected:
ipsets, created by kube-proxy:
So, the proposed changes are:
The text was updated successfully, but these errors were encountered: