You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is slightly different than how Kubernetes integrates with SkyDNS, right? It seems like they plan to run it in pods. I'm curious why we'd take a different approach. I guess we're mostly enabling a easy out of the box integration. The Kubernetes way would likely still work, right?
Is the intention for cluster dns to provide services only for pods? I ask mostly because we'd probably have a few more security requirements if we allow arbitrary clients to contact this service. At a minimum we might want to have some sort of rate limiting.
This is slightly different than how Kubernetes integrates with SkyDNS, right?
Yes, Kubernetes is copying service data into the etcd schema. This bypasses that.
It seems like they plan to run it in pods. I'm curious why we'd take a different approach. I guess we're mostly enabling a easy out of the box integration. The Kubernetes way would likely still work, right?
Efficiency. If we need to we'll eventually have openshift start dns. However, I think this is just something easier to do on the masters.
Is the intention for cluster dns to provide services only for pods? I ask mostly because we'd probably have a few more security requirements if we allow arbitrary clients to contact this service. At a minimum we might want to have some sort of rate limiting.
Check upstream, they do a few things to limit simultaneous queries. However, this is internal cluster focused right now.
—
Reply to this email directly or view it on GitHub.
Nodes will now assume the master is a DNS server (unless OPENSHIFT_DNS_ADDR
is set) and will pass that value in to the containers they run.
The master will listen on 53 (if it can bind to it) or 8053 to serve DNS
queries.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
smarterclayton
force-pushed
the
dns
branch
3 times, most recently
from
Still remaining - add e2e test for services.