Skip to content

Change oc scale command to follow pattern change #514

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 15, 2025
Merged

Change oc scale command to follow pattern change #514

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion content/patterns/medical-diagnosis/cluster-sizing.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,12 +9,15 @@ aliases: /medical-diagnosis/cluster-sizing/
:_content-type: ASSEMBLY
include::modules/comm-attributes.adoc[]

:aws_node: xlarge


//Module to be included
//:_content-type: CONCEPT
//:imagesdir: ../../images
[id="about-openshift-cluster-sizing-med"]
== About OpenShift cluster sizing for the {med-pattern}

{aws_node}
To understand cluster sizing requirements for the {med-pattern}, consider the following components that the {med-pattern} deploys on the datacenter or the hub OpenShift cluster:

|===
Expand Down
8 changes: 4 additions & 4 deletions content/patterns/medical-diagnosis/getting-started.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -340,7 +340,7 @@ You can go to the command-line (make sure you have KUBECONFIG set, or are logged
+
[source,terminal]
----
$ oc scale deploymentconfig/image-generator --replicas=1 -n xraylab-1
$ oc scale deployment/image-generator --replicas=1 -n xraylab-1
----
+
Or you can go to the OpenShift UI and change the view from Administrator to Developer and select Topology. From there select the `xraylab-1` project.
Expand All @@ -357,7 +357,7 @@ image::medical-edge/dev-topology-pod-count.png[link="/images/medical-edge/dev-to
+
Alternatively, you can have the same outcome on the Administrator console.
+
Go to the OpenShift UI under Workloads, select Deploymentconfigs for Project `xraylab-1`.
Go to the OpenShift UI under Workloads, select Deployments for Project `xraylab-1`.
Click `image-generator` and increase the pod count to 1.
+
image::medical-edge/start-image-flow.png[link="/images/medical-edge/start-image-flow.png"]
Expand All @@ -375,14 +375,14 @@ You can change some of the parameters and watch how the changes effect the dashb
+
[source,terminal]
----
$ oc scale deploymentconfig/image-generator --replicas=2
$ oc scale deployment/image-generator --replicas=2
----
+
Check the dashboard.
+
[source,terminal]
----
$ oc scale deploymentconfig/image-generator --replicas=0
$ oc scale deployment/image-generator --replicas=0
----
+
Watch the dashboard stop processing images.
Expand Down
6 changes: 3 additions & 3 deletions content/patterns/medical-diagnosis/troubleshooting.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,16 +59,16 @@ Use the grafana dashboard to assist with debugging and identifying the issue
'''
Problem:: No information is being processed in the dashboard

Solution:: Most often this is due to the image-generator deploymentConfig needing to be scaled up. The image-generator by design is *scaled to 0*;
Solution:: Most often this is due to the image-generator deployment needing to be scaled up. The image-generator by design is *scaled to 0*;
+
[source,terminal]
----
$ oc scale -n xraylab-1 dc/image-generator --replicas=1
$ oc scale -n xraylab-1 deploy/image-generator --replicas=1
----
+
Alternatively, complete the following steps:

. Navigate to the {rh-ocp} web console, and select *Workloads → DeploymentConfigs*
. Navigate to the {rh-ocp} web console, and select *Workloads → Deployments*
. Select `image-generator` and scale the pod to 1 or more.
//AI: Needs review

Expand Down
Loading