Connection timed out from pods within the same cluster

[SanjayVas]

What Happened?

I had to reimage my system and therefore reinstall (rootless) Docker and Minikube. After this, I'm having an issue where my pods within the cluster cannot access each other via ClusterIP services.

I can access these same services from my host machine using kubectl port-forward. I have no issues when applying the same object configurations to a local Kind cluster, or very similar configurations to GKE.

Running Minikube v1.32.0 on Debian Trixie.

Attach the log file

minikube-log.txt

Operating System

Other

Driver

Docker

[SanjayVas]

Can still reproduce in Minikube v1.33.1

[SanjayVas]

After finding #16962, I ended up getting things working by setting net.ipv4.ip_forward=1 on my host machine. It looks like that issue may affect rootless Docker as well.

[k8s-triage-robot]

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/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was 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

[Angelin01]

/remove-lifecycle stale

[k8s-triage-robot]

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/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was 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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[Angelin01]

/remove-lifecycle rotten