Mirrors/coredns
1
0
Fork 0
mirror of https://github.com/coredns/coredns.git synced 2025-10-28 00:34:24 -04:00
Code Issues Packages Projects Releases Wiki Activity

finish docs

Browse Source 
Signed-off-by: Miek Gieben <miek@miek.nl>
This commit is contained in:
Miek Gieben
2020-01-19 09:43:20 +01:00
parent b89d8d7242
commit c8da9cd2dd
1 changed files with 5 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
plugin/traffic/README.md
View File

@@ -79,7 +79,7 @@ traffic TO... {
* `tls_servername` **NAME** allows you to set a server name in the TLS configuration. This is needed * `tls_servername` **NAME** allows you to set a server name in the TLS configuration. This is needed
because *traffic* connects to an IP address, so it can't infer the server name from it. because *traffic* connects to an IP address, so it can't infer the server name from it.
* `ignore_health` can be enabled to ignore endpoint health status, this can aid when debugging. * `ignore_health` can be enabled to ignore endpoint health status, this can aid in debugging.
## Naming Clusters ## Naming Clusters
@@ -91,19 +91,15 @@ and "cluster-v0" is one of the load balanced cluster, *traffic* will respond to
## Metrics ## Metrics
What metrics should we do? If any? Number of clusters? Number of endpoints and health? If monitoring is enabled (via the *prometheus* plugin) then the following metric are exported:
* `coredns_traffic_clusters_tracked{}` the number of tracked clusters.
## Ready ## Ready
This plugin report readiness to the *ready* plugin. This will happen after a gRPC stream has been This plugin report readiness to the *ready* plugin. This will happen after a gRPC stream has been
established to the control plane. established to the control plane.
## Metrics
If monitoring is enabled (via the *prometheus* plugin) then the following metric are exported:
* `coredns_traffic_clusters_tracked{}` the number of tracked clusters.
## Examples ## Examples
~~~ ~~~
@@ -132,10 +128,4 @@ The following documents provide some background on Envoy's control plane.
## Bugs ## Bugs
Priority and locality information from ClusterLoadAssignments is not used. Multiple **TO** addresses Priority and locality information from ClusterLoadAssignments is not used. Multiple **TO** addresses
is not implemented. is not implemented. Credentials are not implemented.
## TODO
* credentials (other than TLS) - how/what?
* is the protocol correctly implemented? Should we not have a 10s tick, but wait for responses from
the control plane?