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

Container under pods can't connect to the internet #88

Closed
MeromTh opened this Issue Oct 17, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@MeromTh

MeromTh commented Oct 17, 2016

I'm trying to run apt-get on your nginx smoke test pods.
Web in smoke test is working, but egress traffic is dead.
I think kube-dns are wrong because

kubectl exec busybox -- nslookup kubernetes.default

and I got

nslookup: can't resolve 'kubernetes.default'
Server:    10.32.0.10
Address 1: 10.32.0.10 kube-dns.kube-system.svc.cluster.local

Did I missed something?

@MeromTh

This comment has been minimized.

Show comment
Hide comment
@MeromTh

MeromTh Oct 17, 2016

FYI pure container, both ingress and egress, work fine.

MeromTh commented Oct 17, 2016

FYI pure container, both ingress and egress, work fine.

font added a commit to font/kubernetes-the-hard-way that referenced this issue Jan 20, 2017

Add firewall rule to allow pods access to PodCIDR
This fixes issue kelseyhightower#88 to allow pods access to PodCIDR such as the case of
DNS. When pods come up with an IP address in the cluster CIDR range,
they cannot access kubedns without a firewall rule to enable it. This
would also prevent pods from accessing each other depending on the
application.

font added a commit to font/kubernetes-the-hard-way that referenced this issue Jan 20, 2017

Add firewall rule to allow pods access to PodCIDR
This fixes issue kelseyhightower#88 to allow pods access to PodCIDR such as the case of
DNS. When pods come up with an IP address in the cluster CIDR range,
they cannot access kubedns without a firewall rule to enable it. This
would also prevent pods from accessing each other depending on the
application.

kelseyhightower added a commit that referenced this issue Mar 23, 2017

Add firewall rule to allow pods access to PodCIDR
This fixes issue #88 to allow pods access to PodCIDR such as the case of
DNS. When pods come up with an IP address in the cluster CIDR range,
they cannot access kubedns without a firewall rule to enable it. This
would also prevent pods from accessing each other depending on the
application.
@kelseyhightower

This comment has been minimized.

Show comment
Hide comment
@kelseyhightower

kelseyhightower Mar 26, 2017

Owner

Firewall rules have been added and we now ensure the right IP tables masquerade rules are in place.

Owner

kelseyhightower commented Mar 26, 2017

Firewall rules have been added and we now ensure the right IP tables masquerade rules are in place.

mbenabda added a commit to weekendesk/kubernetes-the-hard-way that referenced this issue Apr 20, 2018

Add firewall rule to allow pods access to PodCIDR
This fixes issue kelseyhightower#88 to allow pods access to PodCIDR such as the case of
DNS. When pods come up with an IP address in the cluster CIDR range,
they cannot access kubedns without a firewall rule to enable it. This
would also prevent pods from accessing each other depending on the
application.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment