mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-08-07 03:03:59 +00:00
fix buggy example for endpoint specification
This commit is contained in:
parent
c3d92de705
commit
ec3493fd5e
@ -173,7 +173,7 @@ In any of these scenarios you can define a service without a selector:
|
|||||||
}
|
}
|
||||||
```
|
```
|
||||||
|
|
||||||
Because this has no selector, the corresponding `Endpoints` object will not be
|
Because this service has no selector, the corresponding `Endpoints` object will not be
|
||||||
created. You can manually map the service to your own specific endpoints:
|
created. You can manually map the service to your own specific endpoints:
|
||||||
|
|
||||||
```json
|
```json
|
||||||
@ -189,7 +189,7 @@ created. You can manually map the service to your own specific endpoints:
|
|||||||
{ "IP": "1.2.3.4" }
|
{ "IP": "1.2.3.4" }
|
||||||
],
|
],
|
||||||
"ports": [
|
"ports": [
|
||||||
{ "port": 80 }
|
{ "port": 9376 }
|
||||||
]
|
]
|
||||||
}
|
}
|
||||||
]
|
]
|
||||||
@ -200,7 +200,7 @@ NOTE: Endpoint IPs may not be loopback (127.0.0.0/8), link-local
|
|||||||
(169.254.0.0/16), or link-local multicast ((224.0.0.0/24).
|
(169.254.0.0/16), or link-local multicast ((224.0.0.0/24).
|
||||||
|
|
||||||
Accessing a `Service` without a selector works the same as if it had selector.
|
Accessing a `Service` without a selector works the same as if it had selector.
|
||||||
The traffic will be routed to endpoints defined by the user (`1.2.3.4:80` in
|
The traffic will be routed to endpoints defined by the user (`1.2.3.4:9376` in
|
||||||
this example).
|
this example).
|
||||||
|
|
||||||
## Virtual IPs and service proxies
|
## Virtual IPs and service proxies
|
||||||
|
Loading…
Reference in New Issue
Block a user