> [!CAUTION]
> You are currently viewing version 1.8 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](https://docs.cloud.google.com/apigee/docs/hybrid/supported-platforms.md.txt#supported-versions).

<button class="button button-with-icon cloud-select-dropdown__button button-primary" aria-haspopup="true">Version 1.8 (unsupported)</button>

- Supported versions:
- [v1.17 (latest)](https://docs.cloud.google.com/apigee/docs/hybrid/v1.17/multi-org.md.txt)
- [v1.16](https://docs.cloud.google.com/apigee/docs/hybrid/v1.16/multi-org.md.txt)
- [v1.15](https://docs.cloud.google.com/apigee/docs/hybrid/v1.15/multi-org.md.txt)
- [v1.14](https://docs.cloud.google.com/apigee/docs/hybrid/v1.14/multi-org.md.txt)
- [List of supported versions](https://docs.cloud.google.com/apigee/docs/hybrid/supported-platforms.md.txt#supported-versions)
- Unsupported versions:
- [v1.13](https://docs.cloud.google.com/apigee/docs/hybrid/v1.13/multi-org.md.txt)
- [v1.12](https://docs.cloud.google.com/apigee/docs/hybrid/v1.12/multi-org.md.txt)
- [v1.11](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/multi-org.md.txt)
- [v1.10](https://docs.cloud.google.com/apigee/docs/hybrid/v1.10/multi-org.md.txt)
- [v1.9](https://docs.cloud.google.com/apigee/docs/hybrid/v1.9/multi-org.md.txt)
- [v1.8](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/multi-org.md.txt)
- [v1.7](https://docs.cloud.google.com/apigee/docs/hybrid/v1.7/multi-org.md.txt)
- [v1.6](https://docs.cloud.google.com/apigee/docs/hybrid/v1.6/multi-org.md.txt)
- [v1.5](https://docs.cloud.google.com/apigee/docs/hybrid/v1.5/multi-org.html)
- [v1.4](https://docs.cloud.google.com/apigee/docs/hybrid/v1.4/multi-org.html)
- [v1.3](https://docs.cloud.google.com/apigee/docs/hybrid/v1.3/multi-org.html)
- [v1.2](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/multi-org.html)
- [v1.1](https://docs.cloud.google.com/apigee/docs/hybrid/v1.1/multi-org.html)


This topic explains how to add a second Apigee hybrid organization (org) to an existing
Kubernetes cluster. In this multi-org per cluster configuration, both orgs use and share the same Cassandra
ring. Each org can have multiple environments and environment groups configured.

> [!WARNING]
> **Warning:** A multi-org per cluster configuration is supported with specific [limitations](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/multi-org.md.txt#limitations). Until these limitations are mitigated, we do not recommend that you use this configuration.

> [!NOTE]
> **Note:** If you are already using multi-org clusters and would like to migrate the orgs to single org clusters, see [Migrating an org to another cluster](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/migrate-org.md.txt).

## Limitations


A multi-org per cluster configuration is supported with the following limitations. **Until these
limitations are mitigated, we do not recommend that you use this configuration.**

> [!NOTE]
> **Note:** The maximum number of orgs that you can add to a single cluster is limited. See [Limits](https://docs.cloud.google.com/apigee/docs/api-platform/reference/limits.md.txt) for details.

- If you are going to have multiple Apigee hybrid instances, each instance should have its own cluster. Multiple Apigee hybrid instances running on the same kubernetes cluster can lead to issues of instability potentially causing downtime.
- Pod metrics are only sent to the first Google Cloud project that was configured. This limitation is most apparent in the Cloud Monitoring tool. It only affects cluster metrics; API analytics are not affected. The metrics for the other Apigee orgs will not be sent to the matching Google Cloud project.
- All logging from the pods are sent to the first Google Cloud project that was configured. This limitation is most apparent in the Cloud Logging tool. The logs for the other Apigee orgs will not be sent to the matching Google Cloud project. Logs are still captured at the pod level and can be retrieved with `kubectl` commands. However, they are not sent to the correct Cloud project through Cloud Logging.
- You cannot delete org data in the Cassandra database for just one org. This means that you cannot remove orgs selectively. Any modification to the database configuration affects all orgs that are deployed to that cluster.
- The hybrid upgrade procedure upgrades the entire cluster all at once.
- Backup and restore is done as a cluster, and cannot be done for a specific org.
- The Apigee API Monitoring feature (Timeline, Recent, Investigate) only works for the first org that was configured and deployed. It will not work for the other orgs in a multi-org cluster.

## Multi-org options


This section describes how Apigee Support handles existing multi-org clusters and recommendations
for future deployments:

- If you have existing multi-org Kubernetes clusters deployed in non-production and production contexts, Apigee Support will continue to support them. However, note the technical limitations outlined in the next section. We recommend that you change any future production deployments to use one Apigee org per cluster.
- If you have existing multi-org clusters in non-production contexts, Apigee Support will continue to support them. We recommend that you migrate any production clusters to a new configuration that uses one Apigee org per cluster.

## Prerequisites


Before continuing, note the following:

- You must have an existing hybrid org with one or more environments installed and configured in an existing Kubernetes cluster. See the [hybrid installation instructions](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/precog-overview.md.txt).
- When combining multiple orgs in a single cluster, the hybrid versions must all match. Before adding a second org to a cluster, upgrade the existing hybrid installation, if necessary. See [Upgrading Apigee hybrid](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/upgrade.md.txt).

## Create an org to add to the existing cluster


To create the additional org, follow the steps in
[Part 1: Project and org setup.](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/precog-overview.md.txt)

> [!NOTE]
> **Note:** If you have an existing org you want to add to your Apigee hybrid installation, you can skip to [Configure the new
> org](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/multi-org#configuring).

## Configure the new org


In the following steps, you will create a new overrides file and configure it for the
new org.
An `overrides.yaml` file can only support one org's information. Therefore, you must
create a new `overrides.yaml` file and apply it to the existing Kubernetes cluster.

1. Create service accounts for use with the new org. See [Create service accounts](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/install-service-accounts.md.txt).
2. Make note of the TLS certificate files (`.key` and `.pem`) in your `certs` directory. If you need to create them again, you can follow the instructions in [Create TLS certificates](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/install-create-tls-certificates.md.txt).
3. Copy your existing `overrides.yaml` to a new file to use as a starting point for configuring your new org. For example: `new-overrides.yaml`.
4. Edit the new overrides file with the following configurations:

   ```
   org: "new-org-name"
   instanceID: "instance-id"   ## Must match the instanceID of your existing org.

   k8sCluster:
     name: "existing-cluster-name"
     region: "existing-cluster-analytics-region"

   gcp:
     projectID: "new-project-id"
     name: "new-project-id"
     region: "new-project-default-location"

   namespace: namespace ## must be the same for both new and existing orgs

   virtualhosts:
     - name: new-environment-group-name
       sslCertPath: ./certs/cert-file-name # .crt or .pem
       sslKeyPath: ./certs/key-file-name # .key

   envs:
     - name: new-environment-name
       serviceAccountPaths:
         runtime: ./new-service-accounts-directory/new-project-id-apigee-runtime.json
         synchronizer: ./new-service-accounts-directory/new-project-id-apigee-synchronizer.json
         udca: ./new-service-accounts-directory/new-project-id-apigee-udca.json

   connectAgent:
     serviceAccountPath: ./new-service-accounts-directory/new-project-id-apigee-mart.json

   mart:
     serviceAccountPath: ./new-service-accounts-directory/new-project-id-apigee-mart.json

   metrics:
     serviceAccountPath: ./new-service-accounts-directory/new-project-id-apigee-metrics.json

   watcher:
     serviceAccountPath: ./new-service-accounts-directory/new-project-id-apigee-watcher.json
   ```


   The following table describes each of the property values that you must provide in the
   overrides file. For more information, see [Configuration property reference](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/config-prop-ref.md.txt).

   | Variable | Description |
   |---|---|
   | <var translate="no">new-org-name</var> | The name of your new org. |
   | <var translate="no">instance-id</var> | All orgs in in this cluster must have the same instance ID. Therefore this must match the `instanceID` entry in the overrides file for your original org. > [!NOTE] > For multi-region installations, each region requires its own cluster, because individual clusters do not span regions. Therefore, each cluster must have its own unique instance ID shared by every org in the cluster. |
   | <var translate="no">existing-cluster-name</var> | The name of the cluster you are adding this org to. It must match the `k8sCluster.name` entry in the overrides file for your original cluster. |
   | <var translate="no">existing-cluster-analytics-region</var> | The region where the original cluster is provisioned. It must match the `k8sCluster.region` entry in the overrides file for your original cluster. |
   | <var translate="no">new-project-id</var> | The project ID of your new project. The project ID and org name are the same. |
   | <var translate="no">new-project-default-location</var> | The analytics region you specified when you created the new org. It does not have to be the same as the region for the existing org. |
   | <var translate="no">namespace</var> | All orgs in the cluster must share the same namespace. Be sure to use the same namespace that was used for the original org. Note that the default namespace is `apigee`. |
   | <var translate="no">new-environment-group-name</var> | The new environment group you created for the new org. |
   | <var translate="no">cert-file-name</var> and <var translate="no">key-file-name</var> | The TLS cert and key files for the cluster that you checked or created in [step 1](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/multi-org.md.txt#check-tls-files) in this section. |
   | <var translate="no">new-environment-name</var> | The name of the environment you created for the new org. |
   | <var translate="no">new-service-accounts-directory</var> | The directory where the service account key files you created for the new org are located. |

## Apply the configuration


Apply the new org configuration to your cluster:

1. Do a dry run installation to check for any problems:

   ```
   apigeectl apply -f overrides/new-overrides.yaml --org --dry-run=client
   ```

   > [!NOTE]
   > **Note:** It's a good practice to do a dry run before applying the configuration to determine if there are any issues.

2. If there are no issues, apply the org-level components. This step installs the Cassandra jobs (user and schema), Apigee Connect, Apigee Watcher and MART services:

   ```
   apigeectl apply -f overrides/new-overrides.yaml --org
   ```
3. Install the environment. This step installs apigee-runtime, synchronizer and UDCA components, per environment:

   ```
   apigeectl apply -f overrides/new-overrides.yaml --env ${ENV_NAME} --dry-run=client
   ```

   ```
   apigeectl apply -f overrides/new-overrides.yaml --env ${ENV_NAME}
   ```

   > [!NOTE]
   > **Note:** If you have multiple environments in your new org, repeat this step for each environment.

4. Apply the load balancer changes. This step configures the ingress to listen to the new virtual host(s) for the second org:

   > [!WARNING]
   > **Important:** Do not duplicate hostnames/domain names between two orgs, as it can result in unpredictable routing.

   ```
   apigeectl apply -f overrides/new-overrides.yaml --settings virtualhosts --dry-run=client
   ```

   ```
   apigeectl apply -f overrides/new-overrides.yaml --settings virtualhosts
   ```
5. Enable synchronizer access for your new org following the steps in [Enable Synchronizer access](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/install-enable-synchronizer-access.md.txt).