> ## Documentation Index
> Fetch the complete documentation index at: https://docs.resolve.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Kloudfuse

<Info>
  **Prerequisite**: The [Resolve Satellite](/resolve-satellite) should be installed in your environment.
</Info>

## Configure the Kloudfuse integration in Resolve Satellite

Below is an example of how to setup the Kloudfuse integration in the satellite with the url property as well as using the k8s secret (potentially backed by an AWS secret manager or another mechanism) for authentication.

<Steps>
  <Step title="Create a Kubernetes secret">
    Create a Kubernetes secret of the following form. Note that the structure of the secret is important and for Kloudfuse user credentials, it must have the top-level key token: ‘username’ and 'password'.

    ```yaml kloudfuse-resolve-access-secret.yml theme={null}
    apiVersion: v1
    kind: Secret
    type: Opaque
    metadata:
      name:  kloudfuse-resolve-access-secret
    stringData:
      username: "<your kloudfuse username>"
      password: "<your kloudfuse password>"
    ```

    <Warning>
      **Security Best Practice:** Never store credentials in plaintext in configuration files or source control.
      Always use Kubernetes secrets and encrypt etcd or use enterprise secret management systems.
      See [Secret Management](/secret-management) for detailed guidance.
    </Warning>

    To apply the secret run

    ```shell apply secret theme={null}
    kubectl apply -f kloudfuse-resolve-access-secret.yml
    ```
  </Step>

  <Step title="Configure your Kloudfuse credentials in the Resolve Satellite">
    Update your helm values override file with the following information (e.g.: *resolve-values.yaml*)

    ```yaml resolve-values.yaml theme={null}
    integrations:
      kloudfuseIntegration:
        type: kloudfuse
        create: true
        secretName:  "kloudfuse-resolve-access-secret"
        connection:
          url: "<your kloudfuse url>"
    ```

    Install the satellite and apply the values from the yaml file that you have just updated. e.g.: *resolve-values.yaml.* To find the latest version, visit ResolveAI's docker hub repository for the [helm chart](https://hub.docker.com/r/resolveaihq/satellite-chart/tags) and [satellite image](https://hub.docker.com/r/resolveaihq/satellite/tags).

    ```shell apply config to satellite and redeploy theme={null}
    helm upgrade --install oci://registry-1.docker.io/resolveaihq/satellite-chart --version <LatestChart> --values resolve-values.yaml --set image.tag=<LatestImage>
    ```

    Once your satellite is deployed, we will automatically create an integration instance for you.
  </Step>

  <Step title="Verify your integration status in ResolveAI">
    Login to [https://app0.resolve.ai/](https://app0.resolve.ai/). Go to the integrations page and and select “Kloudfuse”

    You should see an automatically created integration based on the provided configuration.
  </Step>
</Steps>

## Mitigation Actions (Optional)

If your organization uses Resolve's [Mitigation Actions](/mitigation-actions) to silence alerts during investigations, your Kloudfuse credentials need additional permissions beyond read-only investigation access.

<Info>
  This section only applies if you have enabled [Mitigation Actions](/mitigation-actions). Read-only credentials are sufficient for investigation.
</Info>

* Configure the integration with credentials that have write access to Kloudfuse's embedded Grafana Alertmanager silences API.
* Read-only credentials can still be used for investigation, but they cannot create or remove silences after human approval.

After updating, verify the integration health check still passes in the Resolve UI.

See [Mitigation Actions](/mitigation-actions) for setup details.