Fixes

bkribbs15 · bkribbs15 · commit b6a0aac9c496 · 2025-08-21T11:47:01.000-06:00
diff --git a/docs/CNAME b/docs/CNAME
@@ -1 +0,0 @@
-
diff --git a/docs/containers/imageregistry.md b/docs/containers/imageregistry.md
@@ -117,42 +117,193 @@ Some examples of an image registry are **Red Hat Quay** and **IBM Cloud Registry
 
 === "Podman"
 
+      **1. Install the Container Registry CLI**
+
+      Before you begin, you need to install the IBM Cloud CLI so that you can run the IBM Cloud ***ibmcloud*** commands.
+      ``` Bash title="Install the container-registry CLI"
+      ibmcloud plugin install container-registry
+      ```
+      **2. Set up a namespace**
+
+      Then, you need to create a namespace. The namespace is created in the resource group that you specify so that you can configure access to resources within the namespace at the resource group level. If you don't specify a resource group, then the default is used.
+      ``` Bash title="Log in to IBM Cloud"
+      ibmcloud login
+      ```
+
+      ``` Bash title="Create namespace"
+      ibmcloud cr namespace-add <my_namespace>
+      ```
+      Make sure to replace <my_namespace\> with your preferred namespace.
+
+      If you want to create the namespace in a specific resource group, use the following code **before** creating the namespace.
+      ``` Bash title="Specify a resource group"
+      ibmcloud target -g <resource_group>
+      ```
+      Replace <resource_group\> with the resource group you want to create the namespace in.
+
+      To validate the namespace was created, run the following command.
+      ``` Bash title="Validate namespace is created"
+      ibmcloud cr namespace-list -v
+      ```
+
+      **3. Pull images from a registry to your local computer**
+
+      Next, you can pull images from IBM Cloud Registry to your local computer. Make sure [Podman](https://podman.io/docs/installation){target="_blank"} is installed and up and running.
+
+      ``` Bash title="Pull image to local computer"
+      podman pull <source_image>:<tag>
+      ```
+      Replace <source_image\> with the respository of the image and <tag\> with the tag of the image that you want to use.
+
+      Below is an example where <source_image\> is "hello-world" and <tag\> is "latest".
+
+      ```
+      podman pull hello-world:latest
+      ```
+
+      **4. Tag the image**
+
+      Tags are used as an optional identifier to specify a particular version of an image.
+
+      ``` Bash title="Tag image"
+      podman tag <source_image>:<tag> <region>.icr.io/<my_namespace>/<new_image_repo>:<new_tag>
+      ```
+      Replace <source_image\> with the respository of the image, <tag\> with the tag of your local image that you previously pulled, <region\> with the name of your region, and <my_namespace\> with the namespace you created in step 2. You'll want to define the repository and tag of the image that you want to use in your namespace by replacing <new_image_repo\> and <new_tag\> respectively.
+
+      Below is an example where <source_image\> is "hello-world", <tag\> is "latest", <region\> is "uk", <my_namespace\> is "namespace1", <new_image_repo\> is "hw_repo", and <new_tag\> is "1".
+
+      ```
+      podman tag hello-word:latest uk.icr.io/namespace1/hw_repo:1
+      ```
+
+      **5. Push images to your namespace**
+
+      First, you'll need to log in to IBM Cloud Container Registry.
+
+      ``` Bash title="Log in to ICR"
+      ibmcloud cr login --client podman
+      ```
+
+      Once you've logged in, you can push the image up to your namespace in the registry.
+
+      ``` Bash title="Push image to your namespace"
+      podman push <region>.icr.io/<my_namespace>/<image_repo>:<tag>
+      ```
+
+      Replace <my_namespace\> with the namespace you created in step 2 and <image_repo\> and <tag\> with the repository and tag of the image you chose when you tagged the image in step 4.
+
+      Below is an example where <region\> is "uk", <my_namespace\> is "namespace1", <image_repo\> is "hw_repo", and <tag\> is "1".
+
+      ```
+      podman push uk.icr.io/namespace1/hw_repo:1
+      ```
+
+      **6. Verify that the image was pushed**
+
+      Verify that the image was pushed successfully by running the comand below.
+
+      ```
+      ibmcloud cr image-list
+      ```
+
+      You can also view your pushed images by clicking on the button below:
+
+      [Images](https://cloud.ibm.com/containers/registry/images){ .md-button target="_blank"}
+
 === "Docker"
 
+      **1. Install the Container Registry CLI**
+
       Before you begin, you need to install the IBM Cloud CLI so that you can run the IBM Cloud ***ibmcloud*** commands.
       ``` Bash title="Install the container-registry CLI"
       ibmcloud plugin install container-registry
       ```
 
+      **2. Set up a namespace**
+
       Then, you need to create a namespace. The namespace is created in the resource group that you specify so that you can configure access to resources within the namespace at the resource group level. If you don't specify a resource group, then the default is used.
       ``` Bash title="Log in to IBM Cloud"
       ibmcloud login
       ```
 
       ``` Bash title="Create namespace"
-      ibmcloud cr namespace-add my_namespace
+      ibmcloud cr namespace-add <my_namespace>
       ```
-      Make sure to replace "my_namespace" with your preferred namespace.
+      Make sure to replace <my_namespace\> with your preferred namespace.
 
       If you want to create the namespace in a specific resource group, use the following code **before** creating the namespace.
       ``` Bash title="Specify a resource group"
-      ibmcloud target -g resource_group
+      ibmcloud target -g <resource_group>
       ```
-      Replace "resource_group" with the resource group you want to create the namespace in.
+      Replace <resource_group\> with the resource group you want to create the namespace in.
 
+      To validate the namespace was created, run the following command.
       ``` Bash title="Validate namespace is created"
       ibmcloud cr namespace-list -v
       ```
 
+      **3. Pull images from a registry to your local computer**
+
       Next, you can pull images from IBM Cloud Registry to your local computer. Make sure [Docker](https://www.docker.com/products/container-runtime/#/download){target="_blank"} is installed and up and running.
 
       ``` Bash title="Pull image to local computer"
-      docker pull source_image:tag
+      docker pull <source_image>:<tag>
       ```
-      Replace "source_image" with ther respository of the image and "tag" with the tag of the image that you want to use. Below is an example.
+      Replace <source_image\> with the respository of the image and <tag\> with the tag of the image that you want to use.
+
+      Below is an example where <source_image\> is "hello-world" and <tag\> is "latest".
 
       ```
       docker pull hello-world:latest
       ```
 
+      **4. Tag the image**
+
+      Tags are used as an optional identifier to specify a particular version of an image.
+
+      ``` Bash title="Tag image"
+      docker tag <source_image>:<tag> <region>.icr.io/<my_namespace>/<new_image_repo>:<new_tag>
+      ```
+      Replace <source_image\> with the respository of the image, <tag\> with the tag of your local image that you previously pulled, <region\> with the name of your region, and <my_namespace\> with the namespace you created in step 2. You'll want to define the repository and tag of the image that you want to use in your namespace by replacing <new_image_repo\> and <new_tag\> respectively.
+
+      Below is an example where <source_image\> is "hello-world", <tag\> is "latest", <region\> is "uk", <my_namespace\> is "namespace1", <new_image_repo\> is "hw_repo", and <new_tag\> is "1".
+
+      ```
+      docker tag hello-word:latest uk.icr.io/namespace1/hw_repo:1
+      ```
+
+      **5. Push images to your namespace**
+
+      First, you'll need to log in to IBM Cloud Container Registry.
+
+      ``` Bash title="Log in to ICR"
+      ibmcloud cr login --client docker
+      ```
+
+      Once you've logged in, you can push the image up to your namespace in the registry.
+
+      ``` Bash title="Push image to your namespace"
+      docker push <region>.icr.io/<my_namespace>/<image_repo>:<tag>
+      ```
+
+      Replace <my_namespace\> with the namespace you created in step 2 and <image_repo\> and <tag\> with the repository and tag of the image you chose when you tagged the image in step 4.
+
+      Below is an example where <region\> is "uk", <my_namespace\> is "namespace1", <image_repo\> is "hw_repo", and <tag\> is "1".
+
+      ```
+      docker push uk.icr.io/namespace1/hw_repo:1
+      ```
+
+      **6. Verify that the image was pushed**
+
+      Verify that the image was pushed successfully by running the comand below.
+
+      ```
+      ibmcloud cr image-list
+      ```
+
+      You can also view your pushed images by clicking on the button below:
+
+      [Images](https://cloud.ibm.com/containers/registry/images){ .md-button target="_blank"}
+
 [Learn More about Quay :fontawesome-brands-redhat:](https://docs.redhat.com/en/documentation/red_hat_quay/3.5/html/deploy_red_hat_quay_for_proof-of-concept_non-production_purposes/pr01){ .md-button target="\_blank"} [Learn More about ICR :fontawesome-solid-cloud:](https://cloud.ibm.com/docs/Registry?topic=Registry-getting-started&interface=ui){ .md-button target="\_blank"}
diff --git a/docs/index.md b/docs/index.md
@@ -2,7 +2,7 @@
 
 ## Bootcamp Overview
 
-This Cloud Native Bootcamp has been created to teach and guide IBMers, Business Partners, and clients what it takes to move to the cloud. We want to provide a way for anyone using this site to come away with some hands-on experience in each of the different technologies listed below. 
+This Cloud Native Bootcamp has been created to teach and guide IBMers, Business Partners, and clients what it takes to move to the cloud. We want to provide a way for anyone using this site to come away with hands-on experience in each of the different technologies listed below. 
 
 
 ## Concepts Covered
@@ -13,7 +13,7 @@ This Cloud Native Bootcamp has been created to teach and guide IBMers, Business
 
     ---
 
-    Moving to the cloud comes with some new concepts and standards that should be understood before starting your journey to cloud. Learn about them by clicking the link below.
+    Moving to the cloud comes with new concepts and standards that should be understood before starting your journey to cloud. Learn about them by clicking the link below.
 
     [:octicons-arrow-right-24: Getting started](./cloud/index.md)
 
@@ -45,4 +45,4 @@ This Cloud Native Bootcamp has been created to teach and guide IBMers, Business
 
 ## How to approach the Bootcamp
 
-This bootcamp has been designed with a 
+This bootcamp has been designed to give the students a better hands-on experience than just copy/paste.  The bootcamp uses the approach of "Read, listen, watch, try it out". We want students to take what they have heard and use their resources to solve the labs on their own without much instruction.
diff --git a/docs/openshift/index.md b/docs/openshift/index.md
@@ -6,6 +6,12 @@ Kubernetes is an open source container orchestration platform that automates dep
 
 ## What is OpenShift?
 
+Red Hat OpenShift is an open-source container platform that runs on the Red Hat enterprise Linux operating system and Kubernetes. It is typically referred to as a "Platform as a Service" (PaaS) due to its combination of services for enterprise businesses, including the Kubernetes platform and Docker container images. OpenShift offers additional features exclusive to its enterprise platform. It allows for deploying apps on highly available clusters and securing hybrid workloads with developer-focused tools and seamless integration of IBM, CloudPak, and Red Hat content.
+
+Red Hat OpenShift provides a uniform platform across public and private clouds for full portability, standardization, and ease of adoption. It offers various forms to meet customer needs, such as Red Hat OpenShift Container Platform (OCP), Red Hat OpenShift Dedicated (OSD), Microsoft Azure Red Hat OpenShift, and Red Hat OpenShift Online.
+
+In summary, Red Hat OpenShift is an enterprise-ready Kubernetes container platform with full-stack automated operations for managing hybrid cloud and multi-cloud deployments. It offers multiple offerings to cater to diverse customer requirements and ensures a consistent experience across public and private clouds.
+
 ## What is Kubernetes?
 
 Kubernetes—also known as ‘k8s’ or ‘kube’—is a container orchestration platform for scheduling and automating the deployment, management, and scaling of containerized applications.
diff --git a/mkdocs.yml b/mkdocs.yml
@@ -22,7 +22,7 @@ theme:
   logo: images/watson-white-logo.png
   favicon: images/watson-white-logo.png
   font:
-    text: IBM Plex Sans Light
+    text: IBM Plex Sans
 plugins:
   - search
   - git-revision-date-localized:
@@ -74,7 +74,7 @@ nav:
           - labs/index.md
           - Containers Lab: labs/containers/index.md
           - Image Registries Lab: labs/containers/container-registry/index.md
-  - <div class="header">Kubernetes/OpenShift</div>:
+  - Kubernetes/OpenShift:
       - openshift/index.md
       - Container Orchestration Concepts: openshift/orchestrationConcepts.md
       - <div class="header">OpenShift Objects</div>:
