-
Notifications
You must be signed in to change notification settings - Fork 468
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
Add support for TXT entries #38
Comments
This isn't horrible, but I am not sure exactly how we would want to support
it.
@bowei
…On Mon, Jan 23, 2017 at 6:23 PM, Rudi C ***@***.***> wrote:
gRPC has a new proposal out for storing service configurations in TXT
records:
grpc/proposal#5 <grpc/proposal#5>
If you use gRPC under Kubernetes, you will now have two choices:
1. use parallel DNS hierarchies, one managed by kube-dns, one by a
more traditional DNS server just for the TXT records
2. extend kube-dns to support custom TXT records
I would prefer the second, by far. This could be accomplished through
either an annotation or a new field on the service. Since I have some
experience with kube-dns, having implemented ExternalName support, I can
help with some/all the code, too. Of course, gRPC is just going to be one
use case for the feature.
This seems to be related to, but still independent from
kubernetes/kubernetes#6437
<kubernetes/kubernetes#6437>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#38>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFVgVOd7DOoO3zGRfmLrdKxwdvy_BpWqks5rVWC_gaJpZM4LrylW>
.
|
@therc -- let's start with a strawman proposal -- you can create a pull request against the docs/specification and proceed from there |
@therc I can help out with this once we have a proposal. |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
gRPC has a new proposal out for storing service configurations in TXT records:
grpc/proposal#5
If you use gRPC under Kubernetes, you will now have two choices:
I would prefer the second, by far. This could be accomplished through either an annotation or a new field on the service. Since I have some experience with kube-dns, having implemented ExternalName support, I can help with some/all the code, too. Of course, gRPC is just going to be one use case for the feature.
This seems to be related to, but still independent from kubernetes/kubernetes#6437
The text was updated successfully, but these errors were encountered: