mirror of https://github.com/k3s-io/k3s
bf2decce81
In many cases clients may wish to view not ready addresses for endpoints in order to do set membership prior to a pod being ready. For instance, a pod that uses the service endpoints to connect to other pods under the same service, but does not want to signal ready before it has contacted at least a minimal number of other pods. This is backwards compatible with old servers and clients. There is an additional cost in size of endpoints before services ramp up, which will add minor CPU and memory use for services that have a significant number of pods which have not become ready. |
||
|---|---|---|
| .. | ||
| api.json | ||
| resourceListing.json | ||
| v1.json | ||
| version.json | ||