From 181cbe0aa7da9cf0bcb708b52ba68f403c62203c Mon Sep 17 00:00:00 2001 From: Gauravpadam <1032201077@tcetmumbai.in> Date: Tue, 16 Jan 2024 22:32:51 +0530 Subject: [PATCH] Styling improvements for scale-intro.md --- .../kubernetes-basics/scale/scale-intro.html | 27 ++++++++++--------- 1 file changed, 15 insertions(+), 12 deletions(-) diff --git a/content/en/docs/tutorials/kubernetes-basics/scale/scale-intro.html b/content/en/docs/tutorials/kubernetes-basics/scale/scale-intro.html index 6a15b53c9e..04dadeed81 100644 --- a/content/en/docs/tutorials/kubernetes-basics/scale/scale-intro.html +++ b/content/en/docs/tutorials/kubernetes-basics/scale/scale-intro.html @@ -17,23 +17,19 @@ description: |-
-
-

Objectives

- -
-
+ +

Objectives

+ +

Scaling an application

Previously we created a Deployment, and then exposed it publicly via a Service. The Deployment created only one Pod for running our application. When traffic increases, we will need to scale the application to keep up with user demand.

If you haven't worked through the earlier sections, start from Using minikube to create a cluster.

-

Scaling is accomplished by changing the number of replicas in a Deployment

- {{< note >}} -

If you are trying this after the previous section, you may have deleted the Service exposing the Deployment. In that case, please expose the Deployment again using the following command:

kubectl expose deployment/kubernetes-bootcamp --type="NodePort" --port 8080

- {{< /note >}} +

Scaling is accomplished by changing the number of replicas in a Deployment.

@@ -47,7 +43,14 @@ description: |-
-
+ +
+
+ {{< note >}} +

If you are trying this after the previous section, you may have deleted the Service exposing the Deployment. In that case, please expose the Deployment again using the following command:

kubectl expose deployment/kubernetes-bootcamp --type="NodePort" --port 8080

+ {{< /note >}} +
+