Add custom DNS settings to service definition#1681
Conversation
Current coverage is 56.07% (diff: 100%)@@ master #1681 diff @@
==========================================
Files 90 90
Lines 14521 14521
Methods 0 0
Messages 0 0
Branches 0 0
==========================================
+ Hits 8137 8143 +6
+ Misses 5297 5292 -5
+ Partials 1087 1086 -1
|
|
/cc @stevvooe |
|
Network options are part of the network, so I am slightly reticent here. (cc @mrjana) Right now, we consider At least, I'd prefer the DNS options to be grouped into a DNS message. I think if we say this is a |
|
After some though, I think Also, please create a TODO indicated that |
18934c0 to
7816b7c
Compare
|
Thanks @aluzzardi @stevvooe. The PR has been updated. Please let me know if there are any issues. |
api/specs.proto
Outdated
| } | ||
|
|
||
| // DNSConfig allows one to specify DNS related configuration in resolv.conf | ||
| DNSConfig dns_config = 15; |
There was a problem hiding this comment.
Can you please give this a customname so that the field name follows Go coding standards?
[(gogoproto.customname) = "DNSConfig"]
There was a problem hiding this comment.
Thanks @aaronlehmann. The PR has been updated.
moby/moby#24391 about allowing custom DNS settings to service definition. This fix adds `DNSConfig` to service definition. This fix is related to the pull request: moby/moby#27567 Signed-off-by: Yong Tang <[email protected]>
7816b7c to
b3be8a0
Compare
|
LGTM It would be good to follow this up with a swarmkit implementation. |
|
LGTM |
This fix tries to fix the issue raised in docker:
moby/moby#24391
about allowing custom DNS settings to service definition.
This fix adds Dns, DnsOptions, DnsSearch to service definition.
This fix is related to the pull request:
moby/moby#27567
Signed-off-by: Yong Tang [email protected]