> For the complete documentation index, see [llms.txt](https://mariadb.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mariadb.com/docs/tools/enterprise/control-center/getting-started/connect/connect-gridgain9-cluster.md).

# Attaching a GridGain 9 Cluster

Attaching a GridGain 9 cluster to Control Center, including secured clusters, Docker deployments, and NAT or load-balancer setups.

This page explains how to attach a GridGain 9 cluster to Control Center.

{% hint style="info" %}
Make sure that Control Center supports the [specific GridGain 9 version](/docs/tools/enterprise/control-center.md#supported-gridgain-9-versions) your cluster is running on.
{% endhint %}

You can attach as many clusters as your license supports.

{% hint style="info" %}
To attach a GridGain 8 cluster, follow [this instruction](/docs/tools/enterprise/control-center/getting-started/connect/connect-gridgain-cluster.md). To attach an Apache Ignite cluster, follow [this instruction](/docs/tools/enterprise/control-center/getting-started/connect/connect-ignite-cluster.md).
{% endhint %}

## Start the Cluster

1. Follow the GridGain 9 documentation to start the cluster.
2. Copy aside the URL address of the cluster as you will need it to connect to the cluster from within Control Center.

Cluster must have open ingress on REST and client ports (`10300` and `10800`, respectively, in the default configuration) for the Control Center backend to connect.

{% hint style="info" %}
While Control Center needs access to the GridGain nodes, these nodes also need to be able to reach Control Center to send metrics.
{% endhint %}

## Enable Connection to Secured Clusters

If your cluster is secured (has SSL/TLS configured), and if it uses self-signed certificates, you need to pass the cluster's trust store parameters to Control Center. This can be done by setting up the `JVM_OPTS` environment variable:

{% code overflow="wrap" %}

```bash
JVM_OPTS=-Xms1g -Xmx2g -server -XX:MaxMetaspaceSize=256m -XX:MaxDirectMemorySize=1g -Djavax.net.ssl.trustStore=/some/local/path/truststore.p12 -Djavax.net.ssl.trustStorePassword=changeit
```

{% endcode %}

## Attach the Cluster to Control Center

To attach the cluster to Control Center:

1. Click the **+** icon on the Control Center toolbar.
2. In he **Attach cluster** dialog that opens, select the **GridGain 9** tab.

   ![Attach GridGain 9 cluster](https://2850516351-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkuTXWg0NDbRx6XUeYpGD%2Fuploads%2Fgit-blob-6b7e942af5a96fbe4b8008789034f711caa49a76%2Fcc-getting-started-attach-cluster-1.png?alt=media)
3. To use an instance of the [Cloud Connector service](/docs/tools/enterprise/control-center/gg9/cloud-connector/connect-cloud-connector.md) (instead of the default Embedded connector), select the required instance from the **Connector** drop-down list.
4. In the **URL of the GridGain REST API** field, enter the cluster URL.
5. If the node you are connecting to is hidden behind an entity like a NAT or a load balancer:
   1. Expand the **Client connections** section.

      ![Attach cluster - Client connections](https://2850516351-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkuTXWg0NDbRx6XUeYpGD%2Fuploads%2Fgit-blob-2f97bb0384625f626c4e7df3be6ab43875366924%2Fcc-getting-started-attach-cluster-3.png?alt=media)
   2. Enter the NAT's or load balancer's address(es) in the **Client connections** field. The format is either `host:port` or `host`. Make sure you have mapped the node address to the NAT/balancer address in the cluster.
6. To enable SSL encryption in Control Center communications with the cluster, select the **SSL enabled** check box.
7. If you are attaching a secure cluster:
   1. Expand the **Cluster credentials** section.

      ![Attach cluster - Cluster credentials](https://2850516351-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkuTXWg0NDbRx6XUeYpGD%2Fuploads%2Fgit-blob-2f97bb0384625f626c4e7df3be6ab43875366924%2Fcc-getting-started-attach-cluster-3.png?alt=media)
   2. Enter **Username** and **Password** that correspond to the credentials of one of the users included in the cluster configuration.
8. Click **Continue**.

   The dialog indicates that the cluster has been found.

   ![GridGain 9 cluster found](https://2850516351-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkuTXWg0NDbRx6XUeYpGD%2Fuploads%2Fgit-blob-8cca519a4dd6616d63b71949cd876febcfcc3e59%2Fcc-getting-started-attach-cluster-2.png?alt=media)
9. Click **Attach**.

The attached cluster displays in the [My cluster](/docs/tools/enterprise/control-center/gg9/dashboard/my-cluster.md) screen.

Its status is `Uninitialized`. You must [initialize the cluster](/docs/tools/enterprise/control-center/gg9/dashboard/my-cluster.md#initializing-the-cluster) to enable monitoring and management activities.

## Attach the Cluster in Docker to Control Center in Docker

1. Install the Cluster as it described in GridGain 9 documentation. Make sure that GridGain 9 utilizes the same network Control Center does, and that the name for the Cluster is defined:

   <pre class="language-bash" data-overflow="wrap"><code class="lang-bash">docker run -d -p 10300:10300 -p 10800:10800 -p 3344:3344 --network control-center --name gridgain  gridgain/gridgain9:latest
   </code></pre>
2. Use the cluster name, e.g., `http://gridgain:10300`, to attach the cluster to Control Center.

## Attach the Cluster in Docker to Control Center Running locally or Vice Versa

1. Find your local IPv4 address.
   1. Use the following command if the cluster and GridGain run on Mac:

      ```bash
      ipconfig getifaddr en0
      ```
   2. Use the following command if the cluster and GridGain run on Linux:

      ```bash
      ip a
      ```
2. Use the address, e.g., `http://192.168.1.16:10300`, to attach the cluster to Control Center.