whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix the command output (#9817)

Browse Source 
I have verified on version v1.11
This commit is contained in:
chenhuan
2018-08-11 20:06:53 +08:00
committed by k8s-ci-robot
parent a567352470
commit 279924ef8e
1 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/debug-application-cluster/debug-service.md
+5 -4
View File
@@ -75,7 +75,7 @@ $ kubectl run hostnames --image=k8s.gcr.io/serve_hostname \
--labels=app=hostnames \ --labels=app=hostnames \
--port=9376 \ --port=9376 \
--replicas=3 --replicas=3
deployment "hostnames" created deployment.apps/hostnames created
``` ```
`kubectl` commands will print the type and name of the resource created or mutated, which can then be used in subsequent commands. `kubectl` commands will print the type and name of the resource created or mutated, which can then be used in subsequent commands.
@@ -134,6 +134,7 @@ So the first thing to check is whether that `Service` actually exists:
```shell ```shell
$ kubectl get svc hostnames $ kubectl get svc hostnames
No resources found.
Error from server (NotFound): services "hostnames" not found Error from server (NotFound): services "hostnames" not found
``` ```
@@ -142,15 +143,15 @@ walk-through - you can use your own `Service`'s details here.
```shell ```shell
$ kubectl expose deployment hostnames --port=80 --target-port=9376 $ kubectl expose deployment hostnames --port=80 --target-port=9376
service "hostnames" exposed service/hostnames exposed
``` ```
And read it back, just to be sure: And read it back, just to be sure:
```shell ```shell
$ kubectl get svc hostnames $ kubectl get svc hostnames
NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
hostnames 10.0.1.175 <none> 80/TCP 5s hostnames ClusterIP 10.0.1.175 <none> 80/TCP 5s
``` ```
As before, this is the same as if you had started the `Service` with YAML: As before, this is the same as if you had started the `Service` with YAML: