k8s-triage-robot
commented
9 months ago The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
haodeon
SanjayVas
What Happened?
I am doing some testing with kind and minikube. I have run into a k8s networking issue which I am hoping someone with more experience can help explain.
I am running rootless podman on Pop_OS! which is based off Ubuntu. When I create a cluster using minikube, pod networking is not working. I initially thought this was a DNS issue but then when I looked at the coredns pod logs it tells me that it cannot reach
192.168.49.1:53: i/o timeout.After further debugging I discover that by enabling
net.ipv4.ip_forwardit all works after recreating the cluster.What is confusing to me is when I use kind to create a cluster it works just fine without
net.ipv4.ip_forwardbeing enabled.From what I can tell minikube and kind are both using kindnet by default. I tried the bridge cni in minikube and it wouldn't work regardless of IP forwarding being enabled or disabled.
Is it intended to require
net.ipv4.ip_forwardto be enabled for minikube with rootless podman to work?How is kind able to work with
net.ipv4.ip_forwarddisabled?Attach the log file
log.txt
Operating System
Ubuntu
Driver
Podman