---
name: satellite-register-openshift-clusters
title: Registering clusters with Satellite Config
description: Location clusters are automatically registered with Satellite Config. Manually register other clusters by running the registration script to set up Satellite Config components.
last-updated: 2026-08-27
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/satellite?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Registering clusters with Satellite Config
{: #register-openshift-clusters}

Location clusters are automatically registered with Satellite Config. Manually register other clusters by running the registration script to set up Satellite Config components.
{: shortdesc}

After you complete these steps, the cluster can be added to a cluster group in your location and [subscribed to Satellite configurations](https://cloud.ibm.com/docs/satellite?topic=satellite-satcon-manage-direct-upload&format=markdown). However, you must still use Red Hat OpenShift on IBM Cloud to manage the worker nodes for these clusters.
{: note}

1. Find the cluster in the public cloud that you want to attach to Satellite Config. To list available clusters, run the `ibmcloud oc cluster ls` command or go to the [Red Hat OpenShift cluster dashboard](https://cloud.ibm.com/kubernetes/clusters?platformType=openshift){: external}.

    Do not manually register clusters that you created in a Satellite location. These clusters are automatically registered with Satellite Config. Registering them again manually can cause issues in your location or cluster.
    {: note}

2. From the Satellite [**Clusters**](https://cloud.ibm.com/satellite/clusters){: external} dashboard, click **Register cluster**.
3. Enter the name of your cluster and click **Register cluster**. Registering a cluster creates an entry in the Satellite Config ConfigMap. However, your cluster cannot be subscribed to a Satellite configuration until you install the Satellite Config agent in your cluster.
4. Copy the command that is displayed to you.
5. [Log in to your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster&format=markdown) and run the command in your cluster. The command creates the `razeedeploy` project, custom resource definitions, and RBAC policies on your cluster that are required to make your cluster visible to Satellite Config.

    Example output
    ```sh
    namespace/razeedeploy created
    serviceaccount/razeedeploy-sa created
    clusterrole.rbac.authorization.k8s.io/razeedeploy-admin-cr created
    clusterrolebinding.rbac.authorization.k8s.io/razeedeploy-rb created
    job.batch/razeedeploy-job created
    ```
    {: screen}

6. Verify that all pods in the `razeedeploy` project are in a `Running` state.

    ```sh
    oc get pods -n razeedeploy
    ```
    {: pre}
    
    Example output 
    ```sh
    NAME                                                  READY     STATUS      RESTARTS   AGE
    clustersubscription-c9cfb6f8b-7p5sw            1/1     Running     0          41m
    encryptedresource-controller-5c68f9746-vhdsk   1/1     Running     0          41m
    mustachetemplate-controller-5f9b554f69-f22v5   1/1     Running     0          41m
    razeedeploy-job-2wbd7                          0/1     Completed   0          47m
    remoteresource-controller-56bbfd6db6-mpngf     1/1     Running     0          41m
    watch-keeper-5d4dd9f56b-bt6jz                  1/1     Running     0          3m41s
    ```
    {: screen}
    
7. Verify your cluster's status on the Satellite [**Clusters**](https://cloud.ibm.com/satellite/clusters){: external} dashboard.
    
8. Optional: Select your cluster to view the Kubernetes resources that are deployed to the cluster.