Comments (12)
So the goal here is to run multiple DNS servers, one for each tenant (inasmuch as you can model the concept)? This intersects really badly with the evolving design of DNS, which was likely to end up with a node-local cache/proxy.
from enhancements.
Proof-of-concept/work-in-progress at https://github.com/ardnaxelarak/kubernetes/tree/31017_namespace_dns_client_config_annotations
from enhancements.
@ardnaxelarak what is the current status of the feature submission? Which milestone does it target?
from enhancements.
Can we target this for 1.6 ?
from enhancements.
@thockin is there a doc describing the DNS you're referring to? Does your "intersect" mean in a "bad" way or just a "big" way? Would a node-local cache imply that pods in different namespaces on the same node would see each other's DNS entries? Seems like a complementary PR would be to make this node-local cache be namespace aware too.
from enhancements.
Doug,
kubernetes/kubernetes#32749 talks about some of
the ideas of installing a cache per-node. That would be fine with
per-namespace DNS policy, but it gets harder in the face of multi-tenancy.
But we're going to have to solve that.
I am OK with the idea of per-namespace DNS policies, but we need a more
thorough proposal that addresses the issues:
- DNSPolicy is currently specced as part of the apiversion
- Annotations are fine for prototyping something like this, but probably
not "for real", but new api objects are sort of under a moratorium - Need to consider how it intersects with caching (positive and negative)
and eventual multi-tenancy
probably more I can't think of.
On Mon, Nov 21, 2016 at 10:38 AM, Doug Davis [email protected]
wrote:
@thockin https://github.com/thockin is there a doc describing the DNS
you're referring to? Does your "intersect" mean in a "bad" way or just a
"big" way? Would a node-local cache imply that pods in different namespaces
on the same node would see each other's DNS entries? Seems like a
complementary PR would be to make this node-local cache be namespace aware
too.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#75 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFVgVOcyuyp2H4WNzcNJhjLiJYk7dLRGks5rAeUrgaJpZM4JsZkB
.
from enhancements.
@thockin Is the per-node DNS cache the place to start prior to this multi-tenant implementation? I'd like to shepherd the latter along while remaining cognizant to the future of DNS.
from enhancements.
from enhancements.
As there's no clear proposal and final decision, I'd skip this one for 1.6 in favor of 1.7 or latter.
from enhancements.
Issues go stale after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Prevent issues from auto-closing with an /lifecycle frozen
comment.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or @fejta
.
/lifecycle stale
from enhancements.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or @fejta
.
/lifecycle rotten
/remove-lifecycle stale
from enhancements.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
from enhancements.
Related Issues (20)
- Redesigning Kubelet Probes HOT 5
- Evacuation API HOT 3
- Optimize retrieving remainingItemCount from etcd for APIServer List chunking calls for performance gain on etcd HOT 7
- Resilient Watchcache Initialization HOT 11
- Move cgroup v1 support into maintenance mode HOT 4
- Condition `PodTerminated` added for pod HOT 1
- Server Feature Gate in etcd HOT 1
- Deprecate & remove Kubelet RunOnce mode HOT 3
- CRI Native Container Copy HOT 3
- Verifying Image Registry Origin in Private Kubernetes Clusters HOT 1
- CEL Variables in Schemas HOT 2
- Dynamics informers for custom CRDS HOT 1
- CEL for CRD AdditionalPrinterColumns HOT 2
- Update Enhancements Repo documentation re: KEP updates
- Audit 1.30 Release for dropped Enhancements post-Enhancements Freeze
- Authorize with Field and Label Selectors HOT 15
- KEP-4603: Tune CrashLoopBackoff HOT 12
- Hot increase cpu/memory/storage without restarting kubelet HOT 3
- NodeLocal DNS Cache Intercepts all dns queiris HOT 3
- KEP-4622: Add a TopologyManager policy option for MaxAllowableNUMANodes HOT 28
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from enhancements.