Getting started

Deploying the MaaS Code Assistant AI Quickstart pattern

Prerequisites

An OpenShift cluster (version 4.20 or later). This pattern requires at least 2 NVIDIA GPU nodes with 48 GB or more of VRAM each.
- AWS: The pattern automatically provisions 2 g6e.2xlarge GPU worker nodes (NVIDIA L40S) during installation. No GPU nodes need to be present before you deploy.
- Other providers and bare metal: GPU nodes must already be part of the OpenShift cluster before you deploy this pattern. The pattern installs all required operators automatically.
- To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console.
- Select OpenShift -> Red Hat OpenShift Container Platform -> Create cluster.
The Helm binary. For instructions, see Installing Helm.
The oc CLI tool. For instructions, see Getting started with the OpenShift CLI.
Additional installation tool dependencies. For details, see Patterns quick start.

Preparing for deployment

Procedure

Fork the ai-quickstart-maas-code-assistant repository on GitHub. You must fork the repository to customize this pattern.

Clone the forked copy of this repository.

$ git clone git@github.com:your-username/ai-quickstart-maas-code-assistant.git

Go to the root directory of your Git repository:
```
$ cd ai-quickstart-maas-code-assistant
```

Run the following command to set the upstream repository:

$ git remote add -f upstream git@github.com:validatedpatterns-sandbox/ai-quickstart-maas-code-assistant.git

Verify the setup of your remote repositories by running the following command:

$ git remote -v

Example output

origin	git@github.com:your-username/ai-quickstart-maas-code-assistant.git (fetch)
origin	git@github.com:your-username/ai-quickstart-maas-code-assistant.git (push)
upstream	git@github.com:validatedpatterns-sandbox/ai-quickstart-maas-code-assistant.git (fetch)
upstream	git@github.com:validatedpatterns-sandbox/ai-quickstart-maas-code-assistant.git (push)

Make a local copy of the secrets template outside of your repository to hold credentials for the pattern.
Do not add, commit, or push this file to your repository. Doing so might expose personal credentials to GitHub.
Run the following command:
```
$ cp values-secret.yaml.template ~/values-secret-ai-quickstart-maas-code-assistant.yaml
```

Populate this file with the user passwords needed for the pattern:

$ vim ~/values-secret-ai-quickstart-maas-code-assistant.yaml

Edit the htpasswd section to set passwords for each user tier:

  - name: htpasswd
    fields:
    - name: admin
      value: <admin-password>
    - name: free-user
      value: <free-user-password>
    - name: premium-user
      value: <premium-user-password>
    - name: enterprise-user
      value: <enterprise-user-password>

Optional: To customize the deployment, create and switch to a new branch by running the following command:
```
$ git checkout -b my-branch
```
Make your changes, then stage and commit them:
```
$ git add <changed-files>
$ git commit -m "Customize deployment"
```
Push the changes to your forked repository:
```
$ git push origin my-branch
```

Deploying the pattern by using the pattern.sh file

To deploy the pattern by using the pattern.sh file, complete the following steps:

Log in to your cluster by following this procedure:
1. Obtain an API token by visiting https://oauth-openshift.apps.<your_cluster>.<domain>/oauth/token/request.
2. Log in to the cluster by running the following command:
  $ oc login --token=<retrieved-token> --server=https://api.<your_cluster>.<domain>:6443
  Or log in by running the following command:
  $ export KUBECONFIG=~/<path_to_kubeconfig>
Deploy the pattern to your cluster. Run the following command:
```
$ ./pattern.sh make install
```

Verification

To verify a successful installation, check the health of the ArgoCD applications:

Run the following command:
```
$ ./pattern.sh make argo-healthcheck
```
It might take several minutes for all applications to synchronize and reach a healthy state. This includes downloading the NVIDIA Nemotron models and configuring the inference endpoints.
Verify that the Operators are installed by navigating to Operators → Installed Operators in the OpenShift Container Platform web console. Confirm the following Operators are present:
- NVIDIA GPU Operator
- Red Hat OpenShift AI
- Red Hat OpenShift DevSpaces
- Red Hat Connectivity Link
After all applications are healthy, verify the inference endpoints are serving by running:
```
$ oc get inferenceservice -A
```
Access the OpenShift DevSpaces dashboard to confirm the IDE environment is available. Navigate to Networking → Routes in the DevSpaces namespace and open the route URL.

Next steps

Edit this page Open a documentation issue