Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Sign in / Register
Toggle navigation
C
Coredns
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Locked Files
Issues
0
Issues
0
List
Boards
Labels
Service Desk
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Security & Compliance
Security & Compliance
Dependency List
License Compliance
Packages
Packages
List
Container Registry
Analytics
Analytics
CI / CD
Code Review
Insights
Issues
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Railgun
Coredns
Commits
5cce32db
Commit
5cce32db
authored
Mar 03, 2020
by
Miek Gieben
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add words on grpc service config
Signed-off-by:
Miek Gieben
<
miek@miek.nl
>
parent
885514b6
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
0 deletions
+4
-0
plugin/traffic/README.md
plugin/traffic/README.md
+4
-0
No files found.
plugin/traffic/README.md
View file @
5cce32db
...
@@ -35,6 +35,10 @@ enough to select the best one. When SRV records are returned, the endpoint DNS n
...
@@ -35,6 +35,10 @@ enough to select the best one. When SRV records are returned, the endpoint DNS n
`endpoint-<N>.<cluster>.<zone>`
that carries the IP address. Querying for these synthesized names
`endpoint-<N>.<cluster>.<zone>`
that carries the IP address. Querying for these synthesized names
works as well.
works as well.
[
gRPC Service Config
](
https://github.com/grpc/proposal/blob/master/A2-service-configs-in-dns.md
)
,
when queried for
`_grpc_config.<cluster> TXT`
such config will be returned. Currently the config
itself is staticly defined from the properties given in the
*traffic*
plugin itself.
Load reporting is not supported for the following reason: A DNS query is done by a resolver.
Load reporting is not supported for the following reason: A DNS query is done by a resolver.
Behind this resolver (which can also cache) there may be many clients that will use this reply. The
Behind this resolver (which can also cache) there may be many clients that will use this reply. The
responding server (CoreDNS) has no idea how many clients use this resolver. So reporting a load of
responding server (CoreDNS) has no idea how many clients use this resolver. So reporting a load of
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment