-
Notifications
You must be signed in to change notification settings - Fork 776
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
Pods without internet connection #1668
Comments
Hi @mutech From the attached tarball I do not see what might be wrong. I see the two CNI related pods up and running but nothing else. Could you reproduce the issue in a generic way (maybe with [1]) and then collect the logs with the [1] https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/ |
Hi @ktsakalozos & thanks for taking the time to look into this! Meanwhile I fiddled around with that installation (installing/uninstalling docker for another purpose which is still seen after I added a pod like this:
Everything that's using http and https fails with timeouts, f.e. Here is the inspect report: So it very much looks like there is an http proxy involved or some protocol specific firewall setup. However I did not consciously setup any nor did I find anything related to it. My original problem with microk8s was to get Eclipse che to work. I initially failed on Ubuntu desktop (where forwarding is not enabled by default and DNS resolution fails first followed by this problem once that was fixed). Here is the related ticket: eclipse-che/che#18128 (comment) (I closed that ticket because I thought fixing the firewall (forward accept) setting solves the problem, but discovered later that http traffic is still not working) |
I found the problem ("DNS works" above was a bit superficial): Running host -v inside the pod:
The NS for Is there a way to keep k8s from using the host domain like this? |
Pods have no access to local network or internet.
That occurs after installing Ubuntu 20.04 (server or desktop - same) and installing microk8s (selecting it in server installation or right after desktop installation finishes).
On an existing installation on Ubuntu 20.04 running in a VMWare VM, the same procedure works after running
sudo iptables -P FORWARD ACCEPT
.The failing installation is on a repurposed iMac 2010. Since it works in the VM, that's probably contributing to the problem, even though I don't really understand why, since networking otherwise works without issues (cable connection, no changing IP addresses)
macws01_inspection-report-20201021_180959.tar.gz
@ktsakalozos (from #1484)
The text was updated successfully, but these errors were encountered: