Skip to content
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

DNS loop when using kind (kubernetes-in-docker) #932

Closed
rohansingh opened this Issue Feb 22, 2019 · 0 comments

Comments

Projects
None yet
1 participant
@rohansingh
Copy link
Contributor

rohansingh commented Feb 22, 2019

Using kind for a local Kubernetes cluster results in a DNS loop similar to #736, since the cluster name is not recognized as "local".

rohansingh added a commit to rohansingh/telepresence that referenced this issue Feb 22, 2019

Fix outbound network access with `kind`
`kind` has the same issue as minikube/minishift, so we need to detect
and handle it the same way.

Fixes telepresenceio#932.

rohansingh added a commit to rohansingh/telepresence that referenced this issue Mar 6, 2019

Fix outbound network access with `kind`
`kind` has the same issue as minikube/minishift, so we need to detect
and handle it the same way.

Fixes telepresenceio#932.

@ark3 ark3 closed this in #933 Apr 1, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.