From c4f9c355ff3a15c8b47c1269dbf1b49a0d2fa67d Mon Sep 17 00:00:00 2001 From: Qiming Teng Date: Mon, 1 Jun 2020 14:19:27 +0800 Subject: [PATCH] Partial fix for debugging service page We are kinda abusing the `{{ note }}` shortcode, which is not meant for lengthy, verbose contents. We should not try include code snippets inside a note. --- .../docs/tasks/debug-application-cluster/debug-service.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/content/en/docs/tasks/debug-application-cluster/debug-service.md b/content/en/docs/tasks/debug-application-cluster/debug-service.md index 23b210cb92..8656f3ae7e 100644 --- a/content/en/docs/tasks/debug-application-cluster/debug-service.md +++ b/content/en/docs/tasks/debug-application-cluster/debug-service.md @@ -61,8 +61,7 @@ kubectl scale deployment hostnames --replicas=3 deployment.apps/hostnames scaled ``` -{{< note >}} -This is the same as if you had started the Deployment with the following +Note that this is the same as if you had started the Deployment with the following YAML: ```yaml @@ -89,7 +88,6 @@ spec: The label "app" is automatically set by `kubectl create deployment` to the name of the Deployment. -{{< /note >}} You can confirm your Pods are running: @@ -195,7 +193,6 @@ hostnames ClusterIP 10.0.1.175 80/TCP 5s Now you know that the Service exists. -{{< note >}} As before, this is the same as if you had started the Service with YAML: ```yaml @@ -218,7 +215,6 @@ spec: 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 Services, these values might be the same. -{{< /note >}} ## Does the Service work by DNS name?