Skip to content

Commit

Permalink
Fix the service printer to be a single line per service
Browse files Browse the repository at this point in the history
  • Loading branch information
@brendandburns
brendandburns committed Aug 10, 2015
1 parent 68bc931 commit 79fb674
Show file tree
Hide file tree
Showing 19 changed files with 123 additions and 133 deletions.
4 changes: 2 additions & 2 deletions docs/getting-started-guides/docker-multinode/testing.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -67,8 +67,8 @@ kubectl expose rc nginx --port=80
This should print:

```console
NAME LABELS SELECTOR IP PORT(S)
nginx <none> run=nginx <ip-addr> 80/TCP
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
nginx 10.179.240.1 <none> 80/TCP run=nginx 8d
```

Hit the webserver:
Expand Down
6 changes: 3 additions & 3 deletions docs/getting-started-guides/docker.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -151,11 +151,11 @@ kubectl expose rc nginx --port=80
This should print:

```console
NAME LABELS SELECTOR IP PORT(S)
nginx run=nginx run=nginx <ip-addr> 80/TCP
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
nginx 10.0.93.211 <none> 80/TCP run=nginx 1h
```

If ip-addr is blank run the following command to obtain it. Know issue #10836
If `CLUSTER_IP` is blank run the following command to obtain it. Know issue #10836

```sh
kubectl get svc nginx
Expand Down
14 changes: 5 additions & 9 deletions docs/getting-started-guides/gce.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -145,15 +145,11 @@ $ kubectl get --all-namespaces services
should show a set of [services](../user-guide/services.md) that look something like this:

```console
NAMESPACE NAME LABELS SELECTOR IP(S) PORT(S)
default kubernetes component=apiserver,provider=kubernetes <none> 10.0.0.1 443/TCP
kube-system kube-dns k8s-app=kube-dns,kubernetes.io/cluster-service=true,kubernetes.io/name=KubeDNS k8s-app=kube-dns 10.0.0.10 53/UDP
53/TCP
kube-system kube-ui k8s-app=kube-ui,kubernetes.io/cluster-service=true,kubernetes.io/name=KubeUI k8s-app=kube-ui 10.0.59.25 80/TCP
kube-system monitoring-grafana kubernetes.io/cluster-service=true,kubernetes.io/name=Grafana k8s-app=influxGrafana 10.0.41.246 80/TCP
kube-system monitoring-heapster kubernetes.io/cluster-service=true,kubernetes.io/name=Heapster k8s-app=heapster 10.0.59.48 80/TCP
kube-system monitoring-influxdb kubernetes.io/cluster-service=true,kubernetes.io/name=InfluxDB k8s-app=influxGrafana 10.0.210.156 8083/TCP
8086/TCP
NAMESPACE NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
default kubernetes 10.0.0.1 <none> 443/TCP <none> 1d
kube-system kube-dns 10.0.0.2 <none> 53/TCP,53/UDP k8s-app=kube-dns 1d
kube-system kube-ui 10.0.0.3 <none> 80/TCP k8s-app=kube-ui 1d
... 8086/TCP
```

Similarly, you can take a look at the set of [pods](../user-guide/pods.md) that were created during cluster startup.
Expand Down
9 changes: 3 additions & 6 deletions docs/getting-started-guides/vagrant.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -227,7 +227,7 @@ $ ./cluster/kubectl.sh get pods
NAME READY STATUS RESTARTS AGE

$ ./cluster/kubectl.sh get services
NAME LABELS SELECTOR IP(S) PORT(S)
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE

$ ./cluster/kubectl.sh get replicationcontrollers
CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS
Expand Down Expand Up @@ -282,11 +282,8 @@ my-nginx-gr3hh 1/1 Running 0 1m
my-nginx-xql4j 1/1 Running 0 1m

$ ./cluster/kubectl.sh get services
NAME LABELS SELECTOR IP(S) PORT(S)

$ ./cluster/kubectl.sh get replicationcontrollers
CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS
my-nginx my-nginx nginx run=my-nginx 3
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
my-nginx 10.0.0.1 <none> 80/TCP run=my-nginx 1h
```

We did not start any services, hence there are none listed. But we see three replicas displayed properly.
Expand Down
9 changes: 5 additions & 4 deletions docs/user-guide/connecting-applications.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -133,7 +133,7 @@ Check your Service:

```console
$ kubectl get svc
NAME CLUSTER IP EXTERNAL IP PORT(S) SELECTOR AGE
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
kubernetes 10.179.240.1 <none> 443/TCP <none> 8d
nginxsvc 10.179.252.126 122.222.183.144 80/TCP,81/TCP,82/TCP run=nginx2 11m
```
Expand Down Expand Up @@ -196,7 +196,7 @@ Kubernetes offers a DNS cluster addon Service that uses skydns to automatically

```console
$ kubectl get services kube-dns --namespace=kube-system
NAME CLUSTER IP EXTERNAL IP PORT(S) SELECTOR AGE
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
kube-dns 10.179.240.10 <none> 53/UDP,53/TCP k8s-app=kube-dns 8d
```

Expand Down Expand Up @@ -413,15 +413,16 @@ Lets now recreate the Service to use a cloud load balancer, just change the `Typ
$ kubectl delete rc, svc -l app=nginx
$ kubectl create -f ./nginx-app.yaml
$ kubectl get svc nginxsvc
NAME CLUSTER IP EXTERNAL IP PORT(S) SELECTOR AGE
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
nginxsvc 10.179.252.126 162.222.184.144 80/TCP,81/TCP,82/TCP run=nginx2 13m
$ curl https://162.22.184.144 -k
...
<title>Welcome to nginx!</title>
```

You can generally tell the external IP of the service, since it will be the one that doesn't start with a `10.*`
The IP address in the `EXTERNAL_IP` column is the one that is available on the public internet. The `CLUSTER_IP` is only available inside your
cluster/private cloud network.

## What's next?

Expand Down
8 changes: 4 additions & 4 deletions docs/user-guide/debugging-services.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -209,16 +209,16 @@ walk-through - you can use your own `Service`'s details here.

```console
$ kubectl expose rc hostnames --port=80 --target-port=9376
NAME LABELS SELECTOR IP(S) PORT(S)
hostnames app=hostnames app=hostnames 80/TCP
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
hostnames 10.0.0.1 <none> 80/TCP run=hostnames 1h
```

And read it back, just to be sure:

```console
$ kubectl get svc hostnames
NAME LABELS SELECTOR IP(S) PORT(S)
hostnames app=hostnames app=hostnames 10.0.1.175 80/TCP
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
hostnames 10.0.0.1 <none> 80/TCP run=hostnames 1h
```

As before, this is the same as if you had started the `Service` with YAML:
Expand Down
2 changes: 0 additions & 2 deletions docs/user-guide/docker-cli-to-kubectl.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -74,8 +74,6 @@ CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS
nginx-app nginx-app nginx run=nginx-app 1
# expose a port through with a service
$ kubectl expose rc nginx-app --port=80 --name=nginx-http
NAME LABELS SELECTOR IP(S) PORT(S)
nginx-http run=nginx-app run=nginx-app 80/TCP
```

With kubectl, we create a [replication controller](replication-controller.md) which will make sure that N pods are running nginx (where N is the number of replicas stated in the spec, which defaults to 1). We also create a [service](services.md) with a selector that matches the replication controller's selector. See the [Quick start](quick-start.md) for more information.
Expand Down
6 changes: 3 additions & 3 deletions docs/user-guide/persistent-volumes/README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -107,9 +107,9 @@ mypod 1/1 Running 0 1h

$ kubectl create -f docs/user-guide/persistent-volumes/simpletest/service.json
$ kubectl get services
NAME LABELS SELECTOR IP(S) PORT(S)
frontendservice <none> name=frontendhttp 10.0.0.241 3000/TCP
kubernetes component=apiserver,provider=kubernetes <none> 10.0.0.2 443/TCP
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
frontendservice 10.0.0.241 <none> 3000/TCP name=frontendhttp 1d
kubernetes 10.0.0.2 <none> 443/TCP <none> 2d
```

## Next steps
Expand Down
11 changes: 7 additions & 4 deletions docs/user-guide/quick-start.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -76,17 +76,20 @@ Through integration with some cloud providers (for example Google Compute Engine

```console
$ kubectl expose rc my-nginx --port=80 --type=LoadBalancer
NAME LABELS SELECTOR IP(S) PORT(S)
my-nginx run=my-nginx run=my-nginx 80/TCP
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
my-nginx 10.179.240.1 <none> 80/TCP run=nginx 8d
```

To find the public IP address assigned to your application, execute:

```console
$ kubectl get svc my-nginx -o json | grep \"ip\"
"ip": "130.111.122.213"
$ kubectl get svc my-nginx
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
my-nginx 10.179.240.1 25.1.2.3 80/TCP run=nginx 8d
```

You may need to wait for a minute or two for the external ip address to be provisioned.

In order to access your nginx landing page, you also have to make sure that traffic from external IPs is allowed. Do this by opening a [firewall to allow traffic on port 80](services-firewalls.md).

## Killing the application
Expand Down
8 changes: 4 additions & 4 deletions examples/cluster-dns/README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -113,8 +113,8 @@ Once that's up you can list the service in the cluster:

```sh
$ kubectl get service dns-backend
NAME LABELS SELECTOR IP(S) PORT(S)
dns-backend <none> name=dns-backend 10.0.236.129 8000/TCP
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
dns-backend 10.0.2.3 <none> 8000/TCP name=dns-backend 1d
```

Again, repeat the same process for prod namespace:
Expand All @@ -123,8 +123,8 @@ Again, repeat the same process for prod namespace:
$ kubectl config use-context prod
$ kubectl create -f examples/cluster-dns/dns-backend-service.yaml
$ kubectl get service dns-backend
NAME LABELS SELECTOR IP(S) PORT(S)
dns-backend <none> name=dns-backend 10.0.35.246 8000/TCP
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
dns-backend 10.0.2.4 <none> 8000/TCP name=dns-backend 1d
```

### Step Four: Create client pod in one namespace
Expand Down
19 changes: 9 additions & 10 deletions examples/guestbook-go/README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -117,8 +117,8 @@ Services find the containers to load balance based on pod labels. The pod that y

```console
$ kubectl get services
NAME LABELS SELECTOR IP(S) PORT(S)
redis-master app=redis,role=master app=redis,role=master 10.0.136.3 6379/TCP
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
redis-master 10.0.136.3 <none> 6379/TCP app=redis,role=master 1h
...
```

Expand Down Expand Up @@ -183,9 +183,9 @@ Just like the master, we want to have a service to proxy connections to the read

```console
$ kubectl get services
NAME LABELS SELECTOR IP(S) PORT(S)
redis-master app=redis,role=master app=redis,role=master 10.0.136.3 6379/TCP
redis-slave app=redis,role=slave app=redis,role=slave 10.0.21.92 6379/TCP
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
redis-master 10.0.136.3 <none> 6379/TCP app=redis,role=master 1h
redis-slave 10.0.21.92 <none> 6379/TCP app-redis,role=slave 1h
...
```

Expand Down Expand Up @@ -246,11 +246,10 @@ Just like the others, we create a service to group the guestbook pods but this t

```
$ kubectl get services
NAME LABELS SELECTOR IP(S) PORT(S)
guestbook app=guestbook app=guestbook 10.0.217.218 3000/TCP
146.148.81.8
redis-master app=redis,role=master app=redis,role=master 10.0.136.3 6379/TCP
redis-slave app=redis,role=slave app=redis,role=slave 10.0.21.92 6379/TCP
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
guestbook 10.0.217.218 146.148.81.8 3000/TCP app=guestbook 1h
redis-master 10.0.136.3 <none> 6379/TCP app=redis,role=master 1h
redis-slave 10.0.21.92 <none> 6379/TCP app-redis,role=slave 1h
...
```

Expand Down
28 changes: 14 additions & 14 deletions examples/guestbook/README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -235,8 +235,9 @@ Then check the list of services, which should include the redis-master:

```console
$ kubectl get services
NAME LABELS SELECTOR IP PORT
redis-master name=redis-master name=redis-master 10.0.246.242 6379
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
redis-master 10.0.136.3 <none> 6379/TCP app=redis,role=master 1h
...
```

This will cause all pods to see the redis master apparently running on <ip>:6379. A service can map an incoming port to any `targetPort` in the backend pod. Once created, the service proxy on each node is configured to set up a proxy on the specified port (in this case port 6379).
Expand Down Expand Up @@ -358,9 +359,9 @@ $ kubectl create -f examples/guestbook/redis-slave-service.yaml
services/redis-slave
$ kubectl get services
NAME LABELS SELECTOR IP PORT
redis-master name=redis-master name=redis-master 10.0.246.242 6379
redis-slave name=redis-slave name=redis-slave 10.0.72.62 6379
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
redis-master 10.0.136.3 <none> 6379/TCP app=redis,role=master 1h
redis-slave 10.0.21.92 <none> 6379/TCP app-redis,role=slave 1h
```

### Step Five: Create the frontend replicated pods
Expand Down Expand Up @@ -525,10 +526,10 @@ Then, list all your services again:

```console
$ kubectl get services
NAME LABELS SELECTOR IP PORT(S)
frontend name=frontend name=frontend 10.0.93.211 80/TCP
redis-master name=redis-master name=redis-master 10.0.246.242 6379/TCP
redis-slave name=redis-slave name=redis-slave 10.0.72.62 6379/TCP
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
frontend 10.0.93.211 <none> 80/TCP name=frontend 1h
redis-master 10.0.136.3 <none> 6379/TCP app=redis,role=master 1h
redis-slave 10.0.21.92 <none> 6379/TCP app-redis,role=slave 1h
```


Expand All @@ -544,11 +545,10 @@ If the `LoadBalancer` specification is used, it can take a short period for an e

```console
$ kubectl get services
NAME LABELS SELECTOR IP PORT(S)
frontend name=frontend name=frontend 10.0.93.211 80/TCP
130.211.135.84
redis-master name=redis-master name=redis-master 10.0.246.242 6379/TCP
redis-slave name=redis-slave name=redis-slave 10.0.72.62 6379/TCP
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
frontend 10.0.93.211 130.211.188.51 80/TCP name=frontend 1h
redis-master 10.0.136.3 <none> 6379/TCP app=redis,role=master 1h
redis-slave 10.0.21.92 <none> 6379/TCP app-redis,role=slave 1h
```

Once you've exposed the service to an external IP, visit the IP to see your guestbook in action. E.g., `http://130.211.188.51:80` in the example above.
Expand Down
6 changes: 4 additions & 2 deletions examples/mysql-wordpress-pd/README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -302,8 +302,10 @@ $ kubectl get services

Then, find the external IP for your WordPress service by running:

```
$ kubectl get services/wpfrontend --template="{{range .status.loadBalancer.ingress}} {{.ip}} {{end}}"
```console
$ kubectl get services/wpfrontend
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
wpfrontend 10.0.0.2 1.2.3.4 80/TCP ... ...
```

or by listing the forwarding rules for your project:
Expand Down
8 changes: 5 additions & 3 deletions examples/phabricator/README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -247,10 +247,12 @@ $ kubectl create -f examples/phabricator/phabricator-service.json
phabricator
```

To play with the service itself, find the external IP of the load balancer:
To play with the service itself, find the `EXTERNAL_IP` of the load balancer:

```sh
$ kubectl get services phabricator -o template --template='{{(index .status.loadBalancer.ingress 0).ip}}{{"\n"}}'
```console
$ kubectl get services phabricator
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
phabricator 10.0.0.2 1.2.3.4 8080/TCP ... ...
```

and then visit port 80 of that IP address.
Expand Down
13 changes: 6 additions & 7 deletions examples/rethinkdb/README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -56,9 +56,9 @@ check out:

```sh
$kubectl get services
NAME LABELS SELECTOR IP(S) PORT(S)
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
rethinkdb-driver 10.0.27.114 <none> 28015/TCP db=rethinkdb 10m
[...]
rethinkdb-driver db=influxdb db=rethinkdb 10.0.27.114 28015/TCP
```

**Step 2**
Expand Down Expand Up @@ -115,13 +115,12 @@ kubectl create -f examples/rethinkdb/admin-service.yaml

find the service

```sh
```console
$kubectl get services
NAME LABELS SELECTOR IP(S) PORT(S)
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
[...]
rethinkdb-admin db=influxdb db=rethinkdb,role=admin 10.0.131.19 8080/TCP
104.197.19.120
rethinkdb-driver db=influxdb db=rethinkdb 10.0.27.114 28015/TCP
rethinkdb-admin 10.0.131.19 104.197.19.120 8080/TCP db=rethinkdb,role=admin 10m
rethinkdb-driver 10.0.27.114 <none> 28015/TCP db=rethinkdb 20m
```

We request an external load balancer in the [admin-service.yaml](admin-service.yaml) file:
Expand Down
Loading

0 comments on commit 79fb674

Please sign in to comment.