# ISD Installation on OpenShift

{% hint style="info" %}
This is an older version of the document. To view the most recent version of the document, click [here](https://docs.opsmx.com/opsmx-context-graph-and-data-fabric/additional-resources/previous-releases/isd-3.12/opsmx-intelligent-software-delivery-platform/opsmx-isd-installation/isd-installation-on-openshift).
{% endhint %}

Refer this detailed instructions for installing ISD on OpenShift platform.

#### **Begin your installation:**

Click Download OES-3.9.1 and README.md. The YAML file for the OES installation and its README will download to your computer.

#### **Pre-requisites**

1. Download and extract the OES Package “tar -xvf OES-.tar.gz”. 
2. Provide the user's quay credentials to get access to the images. 
3. Ensure to have a service account that allows the OES Installation process.

#### **Installation Steps**

1. Navigate to the Directory. 

   `cd OES-/charts/oes`
2. Edit the values.yaml and update the "imageCredentials" as below. 

   `registry: https://quay.io/` 

   `username: # Quay username`

   `password: # Quay password` 

   `email: emailaddress@domain.com # email corresponding to quay` 

   `registry ID`
3. Enable True for the below if needed. 

   3.1)  CertManager 

   3.2)  Ingress 

   3.3)  OpenLDAP
4. If you are using an existing extern Openshift Route/Ingress, ensure to update the URLs in the below fields. So that all the spinnaker and OES configurations will be done during the installation. 

   4.1)  Update the GitOps Halyard Section with BitBucket/S3 where ever Halyard is placed.

   4.2)  Update the Pipeline Promotion with BitBucket/S3 credentials according to your requirement.

   `Spinnaker Deck URL configuration; url overwhich spinnaker deck will be accessed` 

   `Spinnaker Gate URL configuration; url overwhich spinnaker gate will be accessed` 

   `OES-UI url configuration` 

   `OES-Gate url configuration`
5. Update the LDAP details, if you are using a different LDAP.
6. Execute a helm install command to start the installation. 

   `cd OES-/charts/oes/` 

   `helm install oes . --namespace --timeout 20m`

   `E.g. helm install oes . --namespace oes --timeout 20m`
7. After completion of installation, below containers will be up and running.

<table><thead><tr><th width="247">NAME</th><th width="150" align="center">READY</th><th width="150" align="center">STATUS</th><th width="150" align="center">RESTARTS</th><th width="150" align="center">AGE</th></tr></thead><tbody><tr><td>oes-autopilot-787685b89f-tkkjg   </td><td align="center">1/1</td><td align="center">Running</td><td align="center">3</td><td align="center">6h1m</td></tr><tr><td>oes-dashboard-5d4bbb6fcf-x8f7q </td><td align="center">1/1</td><td align="center">Running</td><td align="center">0</td><td align="center">4h13m</td></tr><tr><td><mark style="color:green;">o</mark>es-db-0 </td><td align="center">1/1</td><td align="center">Running</td><td align="center">0</td><td align="center">5h46m</td></tr><tr><td>oes-gate-7b54554c5d-g7qs2</td><td align="center">1/1</td><td align="center">Running</td><td align="center">0</td><td align="center">5h27m</td></tr><tr><td>oes-install-using-hal-nkzkj</td><td align="center">0/1</td><td align="center">Completed</td><td align="center">0</td><td align="center">5h46m</td></tr><tr><td>oes-minio-b56cd74df-srrhd</td><td align="center">1/1</td><td align="center">Running</td><td align="center">0</td><td align="center">10h</td></tr><tr><td>oes-platform-6f55f98c96-72dxd</td><td align="center">1/1</td><td align="center">Running</td><td align="center">0</td><td align="center">5h27m</td></tr><tr><td>oes-redis-master-0</td><td align="center">1/1</td><td align="center">Running</td><td align="center">0</td><td align="center">10h</td></tr><tr><td>oes-sapor-8cf5c9556-d9mpk</td><td align="center">1/1</td><td align="center">Running</td><td align="center">0</td><td align="center">4h15m</td></tr><tr><td>oes-spinnaker-halyard-0</td><td align="center">1/1</td><td align="center">Running</td><td align="center">0</td><td align="center">10h</td></tr><tr><td>oes-ui-6fc95cdf94-mj8fc</td><td align="center">1/1</td><td align="center">Running</td><td align="center">0</td><td align="center">114m</td></tr><tr><td>oes-visibility-889f6fcdb-vcwx7</td><td align="center">1/1</td><td align="center">Running</td><td align="center">4</td><td align="center">6h1m</td></tr><tr><td>opa-67c945d7b7-p9mjw</td><td align="center">1/1</td><td align="center">Running</td><td align="center">0</td><td align="center">7h5m</td></tr><tr><td>spin-clouddriver-caching-6bf67f45b8-wwtcj</td><td align="center">1/1</td><td align="center">Running</td><td align="center">0</td><td align="center">5h37m</td></tr><tr><td>spin-clouddriver-ro-75f8d6bbbd-58fnn</td><td align="center">1/1</td><td align="center">Running</td><td align="center">0</td><td align="center">5h37m</td></tr><tr><td>spin-clouddriver-ro-deck-6b499cd544-69nbt</td><td align="center">1/1</td><td align="center">Running</td><td align="center">0</td><td align="center">5h37m</td></tr><tr><td>spin-clouddriver-rw-6f8ff48976-8c27m</td><td align="center">1/1</td><td align="center">Running</td><td align="center">0</td><td align="center">5h37m</td></tr><tr><td>spin-deck-7f74cd96d5-wcc5n</td><td align="center">1/1</td><td align="center">Running</td><td align="center">0</td><td align="center">5h37m</td></tr><tr><td>spin-echo-scheduler-5fdd9fb7b-m7ztn</td><td align="center">1/1</td><td align="center">Running</td><td align="center">0</td><td align="center">5h37m</td></tr><tr><td>spin-echo-worker-5bf4b855fd-qzpp8</td><td align="center">1/1</td><td align="center">Running</td><td align="center">0</td><td align="center">5h37m</td></tr><tr><td>spin-fiat-59578d97f9-8mhvg</td><td align="center">1/1</td><td align="center">Running</td><td align="center">0</td><td align="center">5h37m</td></tr><tr><td>spin-front50-58c69476b8-pp9g4</td><td align="center">1/1</td><td align="center">Running</td><td align="center">0</td><td align="center">5h37m</td></tr><tr><td>spin-gate-6c6cdfc649-7lgvw</td><td align="center">1/1</td><td align="center">Running</td><td align="center">0</td><td align="center">5h37m</td></tr><tr><td>spin-igor-85d986c45d-dphn5</td><td align="center">1/1</td><td align="center">Running</td><td align="center">0</td><td align="center">5h37m</td></tr><tr><td>spin-orca-7f666f4676-sgbzf</td><td align="center">1/1</td><td align="center">Running</td><td align="center">0</td><td align="center">5h37m</td></tr><tr><td>spin-rosco-69fcc9cd7c-ppjnx</td><td align="center">1/1</td><td align="center">Running</td><td align="center">0</td><td align="center">5h37m</td></tr></tbody></table>

8\. If you are not using any Ingress, create routes for the below services.

`Oes-ui`&#x20;

`Oes-gate`&#x20;

`Spin-deck-lb`&#x20;

`Spin-gate-lb`

9\. After the routes are created, update the URLs in the values.yaml in the ingress section and do a   “helm upgrade”. This will update all the override URLs in the spinnaker and other OES configurations.&#x20;

`Spinnaker Deck URL configuration; url overwhich spinnaker deck will be accessed`&#x20;

`Spinnaker Gate URL configuration; url overwhich spinnaker gate will be accessed`&#x20;

`OES-UI url configuration`&#x20;

`OES-Gate url configuration`

10\. Enter the below command to execute a "helm upgrade"&#x20;

`helm upgrade oes . --namespace oes --timeout 20m`