github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-24 20:24:09 +00:00
Code Issues Projects Releases Wiki Activity

service documentation: fix location of selector in JSON, make it clear that publicIPs belongs in the spec field

Browse Source
This commit is contained in:
Benjamen Keroack 2015-05-06 17:37:31 -07:00
parent 9939f92731
commit 96c5896c74
1 changed files with 10 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
docs/services.md
View File

@ -43,12 +43,15 @@ port 9376 and carry a label "app=MyApp".
"kind": "Service", "kind": "Service",
"apiVersion": "v1beta3", "apiVersion": "v1beta3",
"metadata": { "metadata": {
"name": "my-service" "name": "my-service",
}, "labels": {
"selector": { "environment": "testing"
"app": "MyApp" }
}, },
"spec": { "spec": {
"selector": {
"app": "MyApp"
},
"ports": [ "ports": [
{ {
"protocol": "TCP", "protocol": "TCP",
@ -235,9 +238,9 @@ address.
On cloud providers which support external load balancers, this should be as On cloud providers which support external load balancers, this should be as
simple as setting the `createExternalLoadBalancer` flag of the `Service` spec simple as setting the `createExternalLoadBalancer` flag of the `Service` spec
to `true`. This sets up a cloud-specific load balancer and populates the to `true`. This sets up a cloud-specific load balancer and populates the
`publicIPs` field (see below). Traffic from the external load balancer will be `publicIPs` field of the spec (see below). Traffic from the external load
directed at the backend `Pods`, though exactly how that works depends on the balancer will be directed at the backend `Pods`, though exactly how that works
cloud provider. depends on the cloud provider.
For cloud providers which do not support external load balancers, there is For cloud providers which do not support external load balancers, there is
another approach that is a bit more "do-it-yourself" - the `publicIPs` field. another approach that is a bit more "do-it-yourself" - the `publicIPs` field.