---
name: satellite-ts-satconfig-cluster-access-error
title: Why does the list of Kubernetes resources not show up or update after registering my cluster with Satellite Config?
description: Resolve issues where Kubernetes resources do not appear or update after registering a cluster with Satellite Config.
last-updated: 2026-08-17
---

> ## 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.

# Why does the list of Kubernetes resources not show up or update after registering my cluster with Satellite Config?
{: #satconfig-cluster-access-error}

Resolve issues where Kubernetes resources do not appear or update after registering a cluster with Satellite Config.
{: shortdesc}

When you register a cluster to use with Satellite Config, you do not see the cluster resources show up in the resources list. Even though you subscribe the cluster to a configuration, no Kubernetes resources are created or updated in the cluster.
{: tsSymptoms}

To use a cluster to use with Satellite Config, the proper components must be installed, and you must grant Satellite Config permissions in your cluster to manage Kubernetes resources.
{: tsCauses}

To resolve this issue, follow these steps.
{: tsResolve}

1. Reattach the cluster to Satellite Config. For more information, see [Registering existing Red Hat OpenShift on IBM Cloud clusters with Satellite Config](https://cloud.ibm.com/docs/satellite?topic=satellite-register-openshift-clusters&format=markdown).
    1. Get a `kubectl` command to register your cluster with Satellite Config.
        ```sh
        ibmcloud sat cluster register
        ```
        {: pre}

        Example output
        ```sh
        kubectl apply -f "https://config.satellite.cloud.ibm.com/api/install/razeedeploy-job?orgKey=<orgApiKey>&args=--clustersubscription=<number>&args=--featureflagsetld=<number>&args=--mustachetemplate=<number>&args=--managedset=<number>&args=--remoteresources<number>&args=--remoteresource=<number>&args=--watch-keeper=<number>"
        ```
        {: screen}

    2. Log in to your cluster. If you are not connected to your location host network, include the `--endpoint link` option. For more login options, see [Accessing Red Hat OpenShift clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster&format=markdown).
        ```sh
        ibmcloud oc cluster config -c <cluster_name_or_ID> --admin [--endpoint link]
        ```
        {: pre}

    3. Run the `kubectl` command that you previously retrieved.
2. Grant Satellite Config permissions in your cluster to manage Kubernetes resources. The following command grants `cluster-admin` permissions for the entire cluster. For more options, see [Granting Satellite Config access to your clusters](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfig&format=markdown).
    ```sh
    kubectl create clusterrolebinding razee-cluster-admin --clusterrole=razee-cluster-admin --serviceaccount=razeedeploy:razee-viewer --serviceaccount=razeedeploy:razee-editor --serviceaccount=razeedeploy:razee-satcon
    ```
    {: pre}