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
45ff6dd1
Commit
45ff6dd1
authored
Jul 09, 2020
by
Miek Gieben
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix docs
Signed-off-by:
Miek Gieben
<
miek@miek.nl
>
parent
29acaf73
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
16 deletions
+2
-16
plugin/traffic/README.md
plugin/traffic/README.md
+2
-16
No files found.
plugin/traffic/README.md
View file @
45ff6dd1
...
...
@@ -101,15 +101,11 @@ When a cluster is named this usually consists out of a single word, i.e. "cluste
The
*traffic*
plugins uses the name(s) specified in the Server Block to create fully qualified
domain names. For example if the Server Block specifies
`lb.example.org`
as one of the names,
and "cluster-v0" is one of the load balanced cluster,
*traffic*
will respond to queries asking for
`cluster-v0.lb.example.org.`
and the same goes for
`web`
;
`web.lb.example.org`
.
`cluster-v0.lb.example.org.`
and the same goes for
"web"
;
`web.lb.example.org`
.
For SRV queries all endpoints are returned, the SRV target names are synthesized:
`endpoint-<N>.web.lb.example.org`
to take the example from above.
*N*
is an integer starting with 0.
The gRPC load balancer name:
`_grpclb._tcp.<cluster>.<zone>`
will also be resolved in the same way
as normal SRV queries. gRPC uses this to find load balancers. Note that the addresses returned in
this care are from the management cluster.
## Matching Algorithm
How are clients match against the data we receive from xDS endpoint?
...
...
@@ -150,7 +146,7 @@ This will load balance any names under `lb.example.org` using the data from the
localhost on port 18000. The node ID will be
`test-id`
and no TLS will be used. Assuming a
management server returns config for
`web`
cluster, you can query CoreDNS for it, below we do an
address lookup, which returns an address for the endpoint. The second example shows a SRV lookup
which returns all endpoints.
The third shows what gRPC will ask for when looking for load balancers.
which returns all endpoints.
~~~
sh
$
dig web.lb.example.org +noall +answer
...
...
@@ -164,16 +160,6 @@ web.lb.example.org. 5 IN SRV 100 100 18008 endpoint-2.web.lb.example.org.
endpoint-0.web.lb.example.org. 5 IN A 127.0.1.1
endpoint-1.web.lb.example.org. 5 IN A 127.0.1.2
endpoint-2.web.lb.example.org. 5 IN A 127.0.2.1
$
dig _grpclb._tcp.web.lb.example.org SRV +noall +answer +additional
_grpclb._tcp.web.lb.example.org. 5 IN SRV 100 100 18008 endpoint-0.xds.lb.example.org.
_grpclb._tcp.web.lb.example.org. 5 IN SRV 100 100 18008 endpoint-1.xds.lb.example.org.
_grpclb._tcp.web.lb.example.org. 5 IN SRV 100 100 18008 endpoint-2.xds.lb.example.org.
endpoint-0.xds.lb.example.org. 5 IN A 10.0.1.1
endpoint-1.xds.lb.example.org. 5 IN A 10.0.1.2
endpoint-2.xds.lb.example.org. 5 IN A 10.0.2.1
~~~
## Bugs
...
...
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