diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/README.md b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/README.md new file mode 100644 index 000000000..d27ccf216 --- /dev/null +++ b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/README.md @@ -0,0 +1,31 @@ +# OpenShift Agent-Based Installation + +This repository provides a comprehensive guide for performing an OpenShift Agent-based connected installation. To simplify the process and reduce manual steps, a custom script is included in the bundle to automate resource provisioning. + +This guide is structured into two parts: + +Part 1: Covers the creation of necessary resources and sets up the OpenShift control plane. +Part 2: Focuses on scaling the OpenShift cluster by adding worker nodes to support containerized workloads. + +Reviewed: 05.02.2025 + +# When to use this asset? + +This document is designed for individuals and organizations looking to install OpenShift clusters on Oracle Cloud Infrastructure (OCI) starting from version 4.13 using the Agent-based installation method. + +# Instructions for Utilizing This Asset + +Follow this document as a step-by-step guide to deploy OpenShift on OCI using the Agent-based installation method. + +# Conclusion + +The OpenShift Agent-Based Installation Guide is intended to be a definitive resource for this deployment method. We encourage all users to share feedback, ask questions, and contribute to further improve this project. + +# License + +Copyright (c) 2025 Oracle and/or its affiliates. + +Licensed under the Universal Permissive License (UPL), Version 1.0. + +See [LICENSE](https://github.com/oracle-devrel/technology-engineering/blob/main/LICENSE) for more details. + diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/config-files.zip b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/config-files.zip new file mode 100644 index 000000000..431aad18d Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/config-files.zip differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/agent-based-installation(1:2).md b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/agent-based-installation(1:2).md new file mode 100644 index 000000000..83026c793 --- /dev/null +++ b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/agent-based-installation(1:2).md @@ -0,0 +1,302 @@ +# Install OpenShift Cluster in OCI Using Agent-Based Installation method (1/2) + +This guide walks you through the detailed steps for installing an OpenShift cluster on Oracle Cloud Infrastructure (OCI) using the agent-based installation method. This installation approach is referred to as a connected installation, meaning that both the OpenShift worker and control plane nodes require outbound internet access during the installation process. + +This section is a Part 1 of the "how-to" guide. + +Reviewed: 27.01.2025 + +## High Level Steps + +The following outlines the key steps required to perform the OpenShift agent-based connected installation in Oracle Cloud Infrastructure (OCI): + + + +## Prerequisites + +Before starting, ensure the following: + +- You have access to OCI tenancy with required previliges to provision necessary OCI Infrastructure resources. +- OpenShift Installer + + +## Steps +### 1. Download the OpenShift Client, Installer and Pull Secret + +1. Log in to the **RedHat OpenShift Console** [Red Hat OpenShift Console](https://console.redhat.com/openshift/), go to your cluster list and **Create cluster** +2. Under the Cloud option -> select **Oracle Cloud Infrastructure(virtual machines)** option +3. Select **Local Agent-based** installation method. + + + +4. Download the OpenShift Installer, Pull Secret and Command line interface according to your client operating system. In this example, the MacOS is selected for Installer and the CLI. + + + + + +### 2. Extract the binaries to the client machine + +Extract the OpenShift Installer, CLI and move them to the executable path. + +1. Extract the Openshift Client and move the **kubectl** and **oc** files to **/usr/local/bin** or executable path of your machine. + +2. Extract the OpenShift Installer and move **openshift-install** to your executable path, in this example, it is **/us/local/bin** + + + + +3. Validate the version of OpenShift installer by running the following command. + ``` + openshift-install version + ``` + + +You are all set to start the installation. + +### 3. Create OCI Resources for OpenShift Installation + +1. Create the necessary OCI resources by following the instructions from the documentation below: + +- [OpenShift Installation Pre-Requisites](https://docs.oracle.com/en-us/iaas/Content/openshift-on-oci/install-prereq.htm) + +- [OpenShift Agent Pre-requisites](https://docs.oracle.com/en-us/iaas/Content/openshift-on-oci/agent-prereq.htm) + +1. (**OR**) You can also use the below terraform script to create this resources using OCI Resource Manager stack. The script can be downloaded from the same GitHUb link here + + **oci-openshift-agent-provision-resources.zip** + + 1. Login to the OCI console, select your region and a compartment where you would like to have the resources created. + 2. Navigate to the Hamburger Menu -> Developer Services -> Resource Manager -> Stacks + 3. Click on **Create Stack** -> and upload the zip file **oci-openshift-agent-provision-resources.zip** + 4. Fill in the details to create OCI resources required for the agent-based installation as follows: + 1. cluster_name - name of the OCP cluster + 2. compartment_ocid - this will be automatically populated + 3. enable_private_dns -> Enable + 4. load_balancer_shape_details_maximum_bandwidth_in_mbps - Use default or specify the size + 5. load_balancer_shape_details_minimum_bandwidth_in_mbps - Use default or specify the size + 6. private_cidr - private subnet for the OCP cluster nodes + 7. public_subnet - public subnet for the OCP cluster nodes + 8. region - should auto populate, specify otherwise + 9. tenancy_ocid - should auto populate + 10. vcn_cidr - IPV4 CIDR blocks for the VCN for your OCP cluster + 11. vcn_dns_label - DNS label for VCN (optional) + 12. zone_dns - name of the cluster's DNS zone. The zone_dsn value must be a valid hostname. + 5. click **Run Apply** to create resources + 6. Once after the job is successful, obtain the output by navigating Stacks -> jobs -> output + +Refer to the screenshot below + + + + +**oci_ccm_config** output + + + +### 4. Prepare agent-config.yaml and install-config.yaml files + +Before you begin, make sure to create a directory/folder and maintain the folder structure as shown in the image below. Make sure to create a folder and machine config files where you have extracted openshift installer, client and kubectl. + + In the example below, a folder with name "**demo**" created which contains all the necessary config files. + + + +Now, we will create and update the install-config and agent-config files. + +1. Create and Update the **install-config.yaml**. Copy the contents below and update the details according to your environment. You can also use the sample **config-files.zip** from the GitHub repo. + +``` +apiVersion: v1 +metadata: + name: ocpdemo <-- Replace this with the name of the OCP Cluster +baseDomain: ocpdemo.local <-- Domain name +networking: + clusterNetwork: + - cidr: 10.128.0.0/14 + hostPrefix: 23 + networkType: OVNKubernetes + machineNetwork: + - cidr: 10.50.0.0/16 <-- OCI VCN CIDR + serviceNetwork: + - 172.30.0.0/16 +compute: + - architecture: amd64 + hyperthreading: Enabled + name: worker + replicas: 0 +controlPlane: + architecture: amd64 + hyperthreading: Enabled + name: master + replicas: 3 <-- no. of control plane nodes +platform: + external: + platformName: oci <-- Platform name + cloudControllerManager: External +sshKey: 'ssh-rsa AAAAB3NzaC1yc.......' <-- SSH public key +pullSecret: '{"authsbmNfpreGdyYUp3ZElWYU1FZjAzZjhmTENKUW52MHpDWUJrSDRpUHBQY19aUGtTNWNYQTNmSE9sSnJ0cHRad2xvWHp' <-- Insert pull secret obtained from Step 1.4 + +``` + +2. Update the **agent-config.yaml** + +``` +apiVersion: v1alpha1 +metadata: + name: ocpdemo + namespace: ocpdemo +rendezvousIP: 10.55.16.20 <-- Select free IP from the VCN CIDR. This will be assigned to the first control plane node. +``` + +3. Update the **oci-ccm.yml** + +- You need to update the **oci-ccm-04-cloud-controller-manager-config.yaml** section in the file. Refer to the example screenshot below. + + + +- Obtain the OCID values of a Compartment, VCN, Load Balancer Subnet and Security lists for the resources created in Step 3, if the resources are created manually. +- If you have used the resource manager and a Terraform script to create resources, then you must navigate in OCI console to obtain the value for Hamburger Menu -> Developer Services -> Resource Manager -> Stack -> Open Stack -> Outputs -> copy the values of **oci_ccm-config** Key. + +4. Update the **oci-csi.yml** + +- You need to update the **# oci-csi-01-config.yaml** section in the file. Refer to the example screenshot below. + + + + +- Obtain the OCID values of a Compartment, VCN, Load Balancer Subnet and Security lists for the resources created in Step 3, if the resources are created manually. +- If you have used the terraform script to create resources using resource manager, then you must navigate in OCI console to obtain the value for Hamburger Menu -> Developer Services -> Resource Manager -> Stack -> Open Stack -> Outputs -> copy the values of **oci_ccm-config** Key. + +### 5. Generate Minimum Installation ISO + +To generate the agent ISO file for the OpenShift installation, follow these steps: + +- Navigate to the directory where all the configuration and manifest files are stored. For example, if the files are saved in the "demo" folder, navigate to that folder. + +Run the following command to generate the minimal agent ISO file: + +``` +openshift-install agent create image --log-level debug + +``` +- Replace ./demo with the actual path where your configuration files are stored. This command will create the agent ISO file using the provided configurations. +Once the command completes successfully, the agent ISO file will be generated in the specified directory. + +Refer to the openshift-install agent command line output from the sample screenshot below. + + + +The command will generate the agent ISO along with an **auth** directory. This directory will contain the following important files: + + + +- **kubeconfig** – This file is used to authenticate and configure access to the OpenShift cluster. +- **kubeadmin-password** – This file contains the initial password for the kubeadmin user to access the cluster. +- **rendezvousIP** – This file contains the IP address specified in the agent-config.yaml file, which is used for agent communication. + + + + + +### 5. Create Custom Image in OCI + +1. Login to OCI console and upload the ISO file to OCI Object Storage bucket. +2. Once the upload is successful, create a custom image using **Import image** option. Select **RHEL** Operating system and **QCOW2** image type while importing the ISO. Levae the default selection for Launch mode as **Paravirtualized mode**. Refer to the screenshot below. + + + +3. Once the image is successfully imported, click on **Edit Image Capabilities** and unselect **BIOS** option. Leave the remaining options as default. + + + +### 6. Provision Control Plane Nodes in OCI + +1. Create first OCI instance using custom image created in Step 5. Make sure to use the following setting for the control plane VM. + - Select the flex shape and assign the recommended resources for OCPU and Memory. + - Select the VCN and Private subnet created in Step 3. + - Under Primary VNIC IP addresses - Select **Manually assign private IPv4 address** option and provide the IPv4 address of a **rendezvousIP** supplied in **agent-config.yaml** file. Refer to the sample screenshot below. + + + + - Click on **Use network security groups to control traffic** under Advanced options and select the controlplane NSG. Refer to the sample screenshot below. + + + + - Do not add SSH key as it is already embedded in the ISO supplied in **install-config.yaml** file. + - Modify the boot volume size and VPU based on the Red Hat recommended guidelines. Refer to the example screenshot below + + - Modify the tag namespace in Management tab under advanced option. Use controlplane specific tag namespace, key and a value. Refer to the sample screenshot below. + + + +### 7. Add Control Plane node to the API Apps and Int Load Balancer + +1. In this step, you will be updating the OCI Apps load balancer with new control plane to ensure successful communication with the API listener load balancer. To do that, perform the below tasks: +- Navigate to Hamburger Menu -> Networking -> Virtual Cloud Network(VCN)-> Load Balancer and select **####-openshift_api_apps_lb** load balancer. +- Select the API backend sets -> Backends and Click on **Add backends** to the and add the first control plane node provisioned in Step 6. Refer to the sample screenshot below + + + +- Repeat the steps for HTTP and HTTPS backend sets. + +2. In this step, you will be updating the OCI API Internal load balancer with new control plane node. follow the same procedure as described in step 7.1 and update the **####-openshift_api_int_lb** +3. Create and Update **api_backend**, **infra-mcs** and **infra-mcs_2** with ports **6443**, **26623** & **22624** respectively. + + +### 8. Install OpenShift Cluster + +In this step, you will install the OpenShift from the client machine where you have extracted the **openshift-install** binaries along with **pull secret** and **kubectl** (Step 2). + +1. Run the following command to install the OpenShift cluster + +``` +openshift-install agent wait-for install-complete --log-level debug + +``` +Find below the sample screenshot of the command output. + + + +2. Now, login to the control plane node with the **rendezvous IP** and run the following command to check the logs. + +``` +journalctl -u assisted-service.service +``` + + +**OR** + +``` +journalctl -l + +``` + + + + + +3. Create two additional control plane VMs by following the same procedure you did for Control Plane VM1. + +**Note**: You can use DHCP IP address for the additional Control Plane VMs + +4. Once all the control plane VMs are up, add them to the API Apps and API Int Load balancer. +5. Monitor the progress of **journalctl** command output and logs from openshift-install command. +6. Once the installation is successful, you will see the **Installation Completed** message as an output of the journalctl command. Refer to the screenshot below. + + + +### 9. Validate OpenShift Installation + +1. Navigate to your working directory to identify **auth** directory which contains the two files **kubeadmin-password** and **kubeconfig** +2. Open a browser and access the the openshift console using load balancer DNS name. Refer to the sampel screenshot below. The username is **kubeadmin** and password can be obtained from **kubeadmin-password** file. + + + +3. Validate the status panel. The status should look green and there should not be any alerts. +4. Navigate to the **Compute**-> **Nodes**. The three control plane nodes should appear in **Ready** state without any error messages. Refer to the screeshot below. + + + + +**Note:** Follow the Part 2 of this Tutorial series to complete the OpenShift installation. \ No newline at end of file diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/agent-based-installation(2:2).md b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/agent-based-installation(2:2).md new file mode 100644 index 000000000..7cfa71f74 --- /dev/null +++ b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/agent-based-installation(2:2).md @@ -0,0 +1,132 @@ +# Install OpenShift Cluster in OCI Using Agent-Based Installation method (2/2) + +This guide provides detailed instructions on installing a OpenShift cluster in OCI using agent-based instalation method. This is in continuation of the Part 1 where the control plane nodes are provisioned and the OpenShift cluster is up and running. + +In this section, the worker nodes will be provisioned and joined to the existing cluster. + +Reviewed: 27.01.2025 + +## Prerequisites + +1. Part (1/2) of this installation guide is completed and you have agent based cluster running +2. Webserver to host the Worker ignition files to support the boot process +3. An additional helper VM with the following requirements + 1. Access to the internet + 2. Access to the webserver + 3. OC command line utility + 4. Can access Openshift cluster created in (1/2) +4. Shell script to create worker ignition image [Ignition Create Worker Image Script](https://github.com/davidc-dev/oci-ocp-disconnected-tweaks/blob/main/00-extract-ignition-create-worker-image.sh) + + +## High Level Steps + +1. Prepare Web Server to host the worker ignition file +2. Generate CoreOS RawDisk and Worker ignition file +3. Upload the worker ignition file to the web server +4. Upload the CoreOS RawDisk to the OCI Object Storage and create worker instances +5. Update the API load balancer with the new worker nodes +6. Approve CSRs for the new Worker nodes +7. Validate + + +## Steps +### 1. Prepare Web Server to host the Worker Ignition + +1. You can prepare a web server Apache/Ngix of your choice to host the static contents. Refer to the link for the instructions +- [NGINX Installation](https://docs.oracle.com/en/learn/ol-nginx/) +- [Web Server Static Contents](https://docs.nginx.com/nginx/admin-guide/web-server/serving-static-content/) + +### 2. Generate CoreOS-RawDisk and Worker Ignition file + +1. Download the script from this GitHUb URL and copy it to the helper VM. The link to download the shell script is [Ignition Create Worker Image Script](https://github.com/davidc-dev/oci-ocp-disconnected-tweaks/blob/main/00-extract-ignition-create-worker-image.sh) +2. Modify the script's **Append** section if the static contents are hosted in sub folder. For example, in this example, my static contents are hosted under **downloads** folder from where the worker.ign file will be fetched. If your web server does not have sub folders for the static contents ignore this step. + + + +3. Set the WEBSERVER IP as your web server from the Step 1 and run the script. Once the script is executed successfully, it will generate two files **coreos-rawdisk.raw** and **wroker.ign** + +``` +WEBSERVER= +./00-extract-ignition-create-worker.sh $WEBSERVER + +``` +Refer to the sample screenshot below where the script has generated two files **coreos-rawdisk.raw** and **wroker.ign** files + + + +4. Now, upload the **worker.ign** generated from the previus stage to the webserver hosting static contents. Make sure to test if the **worker.ign** is hosted via web server. Refer to the sample screenshot below. + + + +### 3. Create custom image using Coreos-rawdisk + +In this section, you will create a custom image to provsiion worker instances. to create custom image, follow the steps below: + +1. Login to OCI console and navigate to the Hamburger Menu -> Storage -> Object Storage -> Bucket and upload the **coreos-rawdisk.raw** obtained from the previous step to the bucket. +2. Navigate to the Compute -> Custom Images and click on Import image +3. Provide name of the image, choose the option to **Import from an Object Storage bucket** and select the **coreos-rawdisk.raw** file. +4. Select the image type as **QCOW2** and leave the default settings as-is. +5. Once the image is successfully imported, click on **Edit image capabilities**, and unselect **BIOS** firmware option to save changes. + +### 4. Create worker nodes using custom image and add them to the API Load Balancer + +In this section, you will create worker nodes using the custom image created in Step 3 and add them to the API load balancer. + +1. Create instance using the custom image. Select the compute shape for the CPU and Memory resources required for these worker nodes. + 1. Under networking, select the same VCN and a private subnet where the control plane nodes are deployed. + 2. Leave the default selection of automatic assignments of the IP addresses. + 3. Under Advanced options, select Network Security Group as **cluster-compute-nsg** + 4. Do not Add SSH keys + 5. Add storage as per your requirements. + 6. Review the settings and create worker node. +2. Repeat steps from 4.1 for each additional worker nodes. +3. Once the worker nodes are created, add them to the API Load balancer. Follow the steps below + 1. Navigate to the Hamburger Menu -> networking -> Load balancers -> Open **API Apps** Load balancer. + 2. Open **api_backend** and add all the worker nodes created in step 4.1 & 4.2 with port 6443. + 3. Open **ingress_http** and add all the workder nodes created in step 4.1 & 4.2 with port 80 similarly, update the backend set **ingress_https** with port 443. + +### 5. Approve CSRs for New Worker Nodes and join them to the cluster + +In this section, you need to approve Certificate Signing Requests (CSR) generated by new worker nodes. Once they are approved, the nodes can then join to the cluster successfully. + +1. First check the status of the current active nodes by running the following command. You are expected to see the control plane nodes as a result of a Part 1. Refer to the sample screenshot below + +``` +oc get nodes +``` + + +2. Now run the following command to identify the CSRs which are in pending state. You will see list of the nodes which are pending state. refer to the sample screenshot below + +``` +oc get csr | Pending +``` + + + +3. Approve the CSRs for the worker nodes by running the following command against each pending node. Refer to the sample screenshot below + +``` +oc adm certificate approve +``` + + +Alternatively, approve all pending CSRs at once by running the below command: + +``` +oc get csr -o go-template='{{range .items}}{{if not .status}}{{.metadata.name}}{{"\n"}}{{end}}{{end}}' | xargs --no-run-if-empty oc adm certificate approve +``` + +### 6. Validation + +1. Verify the status of the cluster nodes by running the following command, You are expected to see the worker nodes joined to the cluster with Ready Status. + +``` +oc get nodes +``` + + +2. Login to the openshift console and verify the Status panel shows everything Green. +3. Navigate to the **Compute** -> **Nodes** and verify the worker node status. Refer to the sample screenshot below + + \ No newline at end of file diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/10.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/10.jpg new file mode 100644 index 000000000..a6db342ee Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/10.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/11.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/11.jpg new file mode 100644 index 000000000..151311bd8 Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/11.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/12.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/12.jpg new file mode 100644 index 000000000..207debdb1 Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/12.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/13.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/13.jpg new file mode 100644 index 000000000..98a67443c Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/13.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/16.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/16.jpg new file mode 100644 index 000000000..00d005f15 Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/16.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.1.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.1.jpg new file mode 100644 index 000000000..224562e0b Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.1.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.2.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.2.jpg new file mode 100644 index 000000000..ce9463f1f Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.2.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.3.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.3.jpg new file mode 100644 index 000000000..3679abb9d Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.3.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.4.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.4.jpg new file mode 100644 index 000000000..e68e29243 Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.4.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.5.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.5.jpg new file mode 100644 index 000000000..8dd5ec574 Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.5.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.6.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.6.jpg new file mode 100644 index 000000000..6dbe715b7 Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.6.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.7.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.7.jpg new file mode 100644 index 000000000..01e2c0575 Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.7.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.8.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.8.jpg new file mode 100644 index 000000000..8ac7d20e7 Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.8.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.jpg new file mode 100644 index 000000000..9a5898046 Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/2.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/22.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/22.jpg new file mode 100644 index 000000000..cc2aac0f4 Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/22.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/24.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/24.jpg new file mode 100644 index 000000000..7020aac8d Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/24.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/27.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/27.jpg new file mode 100644 index 000000000..8a2653102 Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/27.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/28-1.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/28-1.jpg new file mode 100644 index 000000000..0b9054f72 Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/28-1.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/28.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/28.jpg new file mode 100644 index 000000000..8a2653102 Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/28.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/29.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/29.jpg new file mode 100644 index 000000000..76f8ab52b Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/29.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/3.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/3.jpg new file mode 100644 index 000000000..411190b2e Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/3.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/30.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/30.jpg new file mode 100644 index 000000000..ecb7b474c Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/30.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/31.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/31.jpg new file mode 100644 index 000000000..d1928072a Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/31.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/32.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/32.jpg new file mode 100644 index 000000000..596381c97 Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/32.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/33.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/33.jpg new file mode 100644 index 000000000..7b7ed970e Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/33.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/34.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/34.jpg new file mode 100644 index 000000000..9fdf0d65c Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/34.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/35.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/35.jpg new file mode 100644 index 000000000..3b419a0a9 Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/35.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/36.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/36.jpg new file mode 100644 index 000000000..3cc1df730 Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/36.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/4.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/4.jpg new file mode 100644 index 000000000..b6e591deb Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/4.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/5.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/5.jpg new file mode 100644 index 000000000..955424bf6 Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/5.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/6.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/6.jpg new file mode 100644 index 000000000..e77ce6d28 Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/6.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/7.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/7.jpg new file mode 100644 index 000000000..bc9fdf547 Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/7.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/8.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/8.jpg new file mode 100644 index 000000000..1069d2e54 Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/8.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/9.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/9.jpg new file mode 100644 index 000000000..4071f4a5e Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/9.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/High-Level Installation Steps.jpg b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/High-Level Installation Steps.jpg new file mode 100644 index 000000000..d65a36a32 Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/High-Level Installation Steps.jpg differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/agent-based installation worklfow.png b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/agent-based installation worklfow.png new file mode 100644 index 000000000..12da58d89 Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/files/images/agent-based installation worklfow.png differ diff --git a/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/oci-openshift-agent-provision-orm.zip b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/oci-openshift-agent-provision-orm.zip new file mode 100644 index 000000000..60e6dd9da Binary files /dev/null and b/cloud-infrastructure/virtualization-solutions/openshift-on-oci/openshift-agent-based-install/oci-openshift-agent-provision-orm.zip differ