Skip to content

Commit 0e00aa7

Browse files
committed
OSDOCS-14351: Updated the text on some diagrams
1 parent 8945b49 commit 0e00aa7

7 files changed

+3
-3
lines changed
Loading
Loading
Loading
-98.5 KB
Binary file not shown.
-120 KB
Binary file not shown.
-147 KB
Binary file not shown.

modules/rosa-hcp-architecture.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,14 +12,14 @@ You can create a ROSA with HCP cluster with or without an internet-facing API se
1212
The worker nodes are deployed in your AWS account and run on your VPC private subnets. You can add additional private subnets from one or more availability zones to ensure high availability. Worker nodes are shared by OpenShift components and applications. OpenShift components such as the ingress controller, image registry, and monitoring are deployed on the worker nodes hosted on your VPC.
1313

1414
.ROSA with HCP architecture
15-
image::ROSA-HCP-architecture-model.png[ROSA with HCP architecture]
15+
image::544_OpenShift_ROSA-HCP_architecture-model.png[ROSA with HCP architecture]
1616

1717
[id="rosa-hcp-network-architecture_{context}"]
1818
== ROSA with HCP architecture on public and private networks
1919
With ROSA with HCP, you can create your clusters on public or private networks. The following images depict the architecture of both public and private networks.
2020

2121
.ROSA with HCP deployed on a public network
22-
image::ROSA-HCP-and-ROSA-Classic-public.png[ROSA with HCP deployed on a public network]
22+
image::544_OpenShift_ROSA-HCP-and-ROSA-Classic-public.png[ROSA with HCP deployed on a public network]
2323

2424
.ROSA with HCP deployed on a private network
25-
image::ROSA-HCP-and-ROSA-Classic-private.png[ROSA with HCP deployed on a private network]
25+
image::544_OpenShift_ROSA-HCP-and-ROSA-Classic-private.png[ROSA with HCP deployed on a private network]

0 commit comments

Comments
 (0)