|
| 1 | +# Install OCI AI Blueprints onto an Existing OKE Cluster |
| 2 | + |
| 3 | +This guide helps you install and use **OCI AI Blueprints** for the first time on an existing OKE cluster that was created outside of blueprints which already has workflows running on it. You will: |
| 4 | + |
| 5 | +1. Ensure you have the correct IAM policies in place. |
| 6 | +2. Retrieve existing cluster OKE and VCN names from console. |
| 7 | +3. Deploy the **OCI AI Blueprints** application onto the existing cluster. |
| 8 | +4. Learn how to add existing nodes in the cluster to be used by blueprints. |
| 9 | + |
| 10 | +--- |
| 11 | + |
| 12 | +## Overview |
| 13 | + |
| 14 | +Rather than installing blueprints onto a new cluster, a user may want to leverage an existing cluster with node pools and tools already installed. This doc will cover the components needed to deploy to an existing cluster, how to add existing node pools to be used by blueprints, and additional considerations which should be considered. |
| 15 | + |
| 16 | +## Step 1: Set Up Policies in Your Tenancy |
| 17 | + |
| 18 | +Some or all of these policies may be in place as required by OKE. Please review the required policies listed [here](docs/iam_policies/README.md) and add any required policies which are missing. |
| 19 | + |
| 20 | +1. If you are **not** a tenancy administrator, ask your admin to add additional required policies in the **root compartment**. |
| 21 | +2. If you **are** a tenancy administrator, you can either manually add the additional policies to an existing dynamic group, or let the resource manager deploy the required policies during stack creation. |
| 22 | + |
| 23 | +## Step 2: Retrieve Existing OKE OCID and VCN OCID |
| 24 | + |
| 25 | +1. Navigate to the console. |
| 26 | +2. Go to the region that contains the cluster you wish to deploy blueprints onto. |
| 27 | +3. Navigate to **Developer Services -> Containers & Artifacts -> Kubernetes Clusters (OKE) -> YourCluster** |
| 28 | +4. Click your cluster, and then capture the name of the cluster and the name of the VCN as they will be used during stack creation. |
| 29 | + |
| 30 | +## Step 3: Deploy the OCI AI Blueprints Application |
| 31 | + |
| 32 | +1. Go to [Deploy the OCI AI Blueprints Application](./GETTING_STARTED_README.md#step-3-deploy-the-oci-ai-blueprints-application) and click the button to deploy. |
| 33 | +2. Go to the correct region where your cluster is deployed. |
| 34 | +3. If you have not created policies and are an admin, and would like the stack to deploy the policies for you: |
| 35 | + |
| 36 | + - select "NO" for the question "Have you enabled the required policies in the root tenancy for OCI AI Blueprints?" |
| 37 | + - select "YES" for the question "Are you an administrator for this tenancy?". |
| 38 | + - Under the section "OCI AI Blueprints IAM", click the checkbox to create the policies. (If you do not see this, ensure you've selected the correct choices for the questions above.) |
| 39 | + |
| 40 | +- Otherwise, create the policies if you are an admin, or have your admin create the policies. |
| 41 | +4. Select "YES" for all other options. |
| 42 | +5. Fill out additional fields for username and password, as well as Home Region. |
| 43 | +6. Under "OKE Cluster & VCN", select the cluster name and vcn name you found in step 2. |
| 44 | +7. Populate the subnets with the appropriate values. As a note, there is a "hint" under each field which corresponds to possible naming conventions. If your subnets are named differently, navigate back to the console page with the cluster and find them there. |
| 45 | +8. **Important**: uncheck any boxes for "add-ons" which you already have installed. The stack will fail if a box is left checked and you already have the tool installed in any namespace. |
| 46 | + - if you leave a box checked and the stack fails: |
| 47 | + - click on stack details at the top |
| 48 | + - click on variables |
| 49 | + - Click "Edit variables" box |
| 50 | + - Click "Next" |
| 51 | + - Fill the drop downs back in at the top (the rest will persist) |
| 52 | + - Uncheck the box of the previously installed application. |
| 53 | + - Click "Next" |
| 54 | + - Check the "Run apply" box" |
| 55 | + - Click "Save changes" |
| 56 | + - **Currently autoscaling requires prometheus to be installed in the `cluster-tools` namespace** and keda in the `default` namespace. This will change in an upcoming release. |
| 57 | + |
| 58 | +## Step 4: Add Existing Nodes to Cluster (optional) |
| 59 | +If you have existing node pools in your original OKE cluster that you'd like Blueprints to be able to use, follow these steps after the stack is finished: |
| 60 | + |
| 61 | +1. Go to the stack and click "Application information". Click the API Url. |
| 62 | + - If you get a warning about security, sometimes it takes a bit for the certificates to get signed. This will go away once that process completes on the OKE side. |
| 63 | +2. Login with the `Admin Username` and `Admin Password` in the Application information tab. |
| 64 | +3. |
0 commit comments