mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
32 lines
1.2 KiB
Plaintext
32 lines
1.2 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * tutorials/dev-app-web-console.adoc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="getting-started-web-console-scaling-app_{context}"]
|
|
= Scaling up the application
|
|
|
|
In Kubernetes, a `Deployment` object defines how an application deploys. In most cases when you deploy an application, {product-title} creates the `Pod`, `Service`, `ReplicaSet`, and `Deployment` resources for you.
|
|
|
|
When you deploy the `parksmap` image, a deployment resource is created. In this example, only one pod is deployed. You might want to scale up your application to keep up with user demand or to ensure that your application is always running even if one pod is down.
|
|
|
|
The following procedure scales the `parksmap` deployment to use two instances.
|
|
|
|
.Prerequisites
|
|
|
|
* You have deployed the `parksmap` front-end application.
|
|
|
|
.Procedure
|
|
|
|
. Navigate to *Workloads* -> *Topology* and click the `parksmap` deployment.
|
|
. Select the *Details* tab.
|
|
. Use the up arrow to scale the pod to two instances.
|
|
+
|
|
.Scaling application
|
|
image::getting-started-scaling-pod.png[Scaling pod to two instances]
|
|
|
|
[TIP]
|
|
====
|
|
You can use the down arrow to scale your deployment back down to one pod instance.
|
|
====
|