Merge pull request #6 from RedHatQuickCourses/Technical-Edits

Adjusting Image Width
RedHatQuickCourses · Jun 12, 2024 · f0e4aa8 · f0e4aa8
2 parents 06edc31 + 8ed76e8
commit f0e4aa8
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 6 deletions.
diff --git a/modules/chapter2/pages/section1.adoc b/modules/chapter2/pages/section1.adoc
@@ -34,7 +34,7 @@ This exercise uses the Red Hat Demo Platform; specifically the OpenShift Contain
 
 * Navigate to **Operators** -> **OperatorHub** and search for *OpenShift AI*.
 
-image::openshiftai_operator.png[]
+image::openshiftai_operator.png[width=640]
 
 . Click on the `Red{nbsp}Hat OpenShift AI` operator. In the pop up window that opens, ensure you select the latest version in the *stable* channel and click on **Install** to open the operator's installation view.
 +

diff --git a/modules/chapter2/pages/section2.adoc b/modules/chapter2/pages/section2.adoc
@@ -25,7 +25,7 @@ The content of the Secret (data) should contain two items, *tls.cert* and *tls.k
     . From the Project dropdown, toggle the *show default projects* radial button to on. 
     . Select the *openshift-ingress* project from the list. 
 
-image::openshiftingress_project.png[]
+image::openshiftingress_project.png[width=640]
 
     . Locate the file named *ingress-certs-(XX-XX-2024)*, type should be *Opaque*
     . Click on the filename to open the secret, Select the *YAML Tab*
@@ -51,7 +51,7 @@ tls.key: >-
     LS0tLS1CRUd...
 type: kubernetes.io/tls
 ```
-image::createsecret.png[]
+image::createsecret.png[width=640]
 
 
 * Copy the name of the secret from line 4, just the name  (optional, but helpful)
@@ -86,12 +86,11 @@ serving:
     managementState: Managed
     name: knative-serving
 ```
-image::dcsyamlfile.png[]
+image::dcsyamlfile.png[width=640]
 
 Once you have made those changes to the YAML file, *Click Create* to Deploy the Data Science Cluster.  
 
-
-image::createDSC.png[]
+image::createDSC.png[width=640]
 
 Single Model Serve Platform will now be deployed to expose ingress connections with the same certificate as OpenShift Routes. Endpoints will be accessible using TLS without having to ignore error messages or create special configurations.