---
name: satellite-ts-addon-errors
title: Why doesn't my cluster add-on work?
description: Resolve issues with cluster add-ons in IBM Cloud Satellite, including add-ons that are unsupported, unhealthy, or misconfigured.
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 doesn't my cluster add-on work?
{: #addon-errors}
{: troubleshoot}
{: support}

Resolve issues with cluster add-ons in IBM Cloud Satellite, including add-ons that are unsupported, unhealthy, or misconfigured.
{: shortdesc}

When you try to use a cluster add-on in IBM Cloud Satellite®, the cluster add-on does not work. For example, you installed the Kubernetes web terminal add-on but cannot open the add-on.
{: tsSymptoms}

Add-ons might not work for several reason.
{: tsCauses}

- The add-on is not supported for clusters in a Satellite location.
- The add-on is in an unhealthy state.
- The add-on settings are misconfigured, such as renaming or editing a ConfigMap.
- The add-on cannot be backed up in IBM Cloud Object Storage due to conflicting service instance and bucket endpoints.

Take the following steps to troubleshoot the add-on.
{: tsResolve}

1. Check that the [add-on is supported](https://cloud.ibm.com/docs/openshift?topic=openshift-managed-addons&format=markdown#addons-satellite). If not, uninstall the add-on.
2. If the add-on is misconfigured, refresh the cluster master to restore the add-on to the default settings. 
    ```sh
    ibmcloud oc cluster master refresh -c CLUSTER_NAME_OR_ID
    ```
    {: pre}

3. If the add-on is in critical state, review the IBM Cloud Object Storage instance and bucket that backs up the cluster data. The instance and endpoint must have matching endpoints, such as a **Global** instance with a **Cross Region** bucket (`us-geo` endpoint), or a **Regional** instance with a **Regional** bucket (`us-east` endpoint). If the endpoints do not match, you must re-create the Satellite location with matching IBM Cloud Object Storage instance and bucket endpoints.
4. For more information, [review the add-on state and statuses](https://cloud.ibm.com/docs/openshift?topic=openshift-debug_addons&format=markdown).