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

Merge pull request #21390 from tengqm/fix-service-note

Browse Source 
Partial fix for debugging service page
This commit is contained in:
Kubernetes Prow Robot
2020-06-01 03:59:54 -07:00
committed by GitHub
parent 1b9c4c2b4d c4f9c355ff
commit b1c42abce1
1 changed files with 1 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/debug-application-cluster/debug-service.md
+1 -5
View File
@@ -61,8 +61,7 @@ kubectl scale deployment hostnames --replicas=3
deployment.apps/hostnames scaled deployment.apps/hostnames scaled
``` ```
{{< note >}} Note that this is the same as if you had started the Deployment with the following
This is the same as if you had started the Deployment with the following
YAML: YAML:
```yaml ```yaml
@@ -89,7 +88,6 @@ spec:
The label "app" is automatically set by `kubectl create deployment` to the name of the The label "app" is automatically set by `kubectl create deployment` to the name of the
Deployment. Deployment.
{{< /note >}}
You can confirm your Pods are running: You can confirm your Pods are running:
@@ -195,7 +193,6 @@ hostnames ClusterIP 10.0.1.175 <none> 80/TCP 5s
Now you know that the Service exists. Now you know that the Service exists.
{{< note >}}
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:
```yaml ```yaml
@@ -218,7 +215,6 @@ spec:
In order to highlight the full range of configuration, the Service you created In order to highlight the full range of configuration, the Service you created
here uses a different port number than the Pods. For many real-world here uses a different port number than the Pods. For many real-world
Services, these values might be the same. Services, these values might be the same.
{{< /note >}}
## Does the Service work by DNS name? ## Does the Service work by DNS name?