> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/admin-guide/33/how-to-guides/openshift-provision-tenant-projects.md).

# Provision tenant projects OpenShift

This guide shows you how to set up tenant projects on Openshift clusters. If you try to provision tenant projects using the [normal provisioning flow](/admin-guide/33/deployment-patterns/projects.md), Central Console cannot reach the host where Supervisor Console runs. Failing to follow these steps can lead an 'Internal Server Error', even when everything seems to be set up properly.

<figure><img src="/files/sFdm2BxuE07KYdMUk8PE" alt="openshift provision tenant projects error"><figcaption></figcaption></figure>

In this example provisioning flow, the DNS names for Central Console and Supervisor Console are:

* Central Console — <https://console.apps.jonathan.lab.twistlock.com>
* Supervisor Console to be provisioned — <https://console.39apps.jonathan.lab.twistlock.com>

**Prerequisites:**

* Two fully operational Prisma Cloud Consoles are already deployed. For more information, see the [OpenShift 4](/admin-guide/33/install/deploy-console/console-on-openshift.md) deployment.
* OpenShift external routes to both Consoles' TCP port 8083 (Prisma Cloud UI and API), with the TLS termination type set to passthrough, already exist.
* The to-be Central and Supervisor Consoles are already licensed and you’ve created initial admin users.

1. Designate one Console to be Supervisor and the other to be Central.
2. Log into the Supervisor Console with your admin user.
3. Add the FQDN of the Supervisor Console to the Subject Alternative Name field of the Supervisor Console’s certificate.
   1. In the Supervisor Console, go to **Manage > Defenders > Names**.
   2. Click **Add SAN**.
   3. Add the Supervisor Console’s FQDN. In this example, it is **console.39apps.jonathan.lab.twistlock.com**.
   4. Click **Add**.

      <figure><img src="/files/nrbD4oikXSkG7tduZzux" alt="openshift provision tenant projects san"><figcaption></figcaption></figure>
4. Log into the Central Console with your admin user.
5. Enable Projects by going to **Manage > Projects > Manage** and setting **Use Projects** to **On**.
6. Click the **Provision** tab and to provision a tenant Console.
   1. Under **Select Project type**, choose **Tenant**.
   2. In **Project name**, give your project a name.
   3. In **Supervisor address**, add the FQDN of the Supervisor. In this example, it is <https://console.39apps.jonathan.lab.twistlock.com>.
   4. Add the **Admin credentials for Supervisor**.
   5. Click **Provision**.

      Your Supervisor Console should be successfully provisioned.

      <figure><img src="/files/tV4kQJt440NTCX9OcF9c" alt="openshift provision tenant projects provisioned"><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.prismacloud.io/admin-guide/33/how-to-guides/openshift-provision-tenant-projects.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
