> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/content-collections/administration/network-security/container-network-exposure/deploy-satellite.md).

# Satellite Deployment

You can deploy Satellite manually or automated using the UI or the API.

The deployment of the Satellite operator across multiple namespaces within the same cluster is not supported. If you remove the Satellite operator from the Kubernetes cluster, the Kubernetes data that is ingested through that operator is immediately deleted.

1. Select **Settings > Providers**
2. Click Connect Provider and select **K8s Satellite**.
3. Enter the Cluster **Name** or Resource **ID** in the **K8s Cluster ID** dropdown.
4. (Optional) Enter **Username** and **Password**.
5. Click **Next**.

   You can search the cluster by its name or the unique cluster asset ID by referencing the Cluster Asset ID field on the Asset Inventory page.

   <figure><img src="https://3990409212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyqPwsbMSaogAot23rTIu%2Fuploads%2Fgit-blob-175ef966ef140754b3d06dc594787671c939ad07%2Fk8s-deploy-satellite-1.png?alt=media" alt="k8s deploy satellite 1"><figcaption></figcaption></figure>
6. **Review** the Cluster details and click **Next**.

   <figure><img src="https://3990409212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyqPwsbMSaogAot23rTIu%2Fuploads%2Fgit-blob-82c3b88bad230e6ef41633b97767331b3c535b52%2Fk8s-deploy-satellite-2.png?alt=media" alt="k8s deploy satellite 2"><figcaption></figcaption></figure>
7. Copy the **Helm** upgrade/install command and run it in your selected cluster.

   A unique identifier is created each time a Helm chart is generated and it acts as a cluster identifier. Therefore, you cannot reuse the Helm chart across different clusters.

   <figure><img src="https://3990409212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyqPwsbMSaogAot23rTIu%2Fuploads%2Fgit-blob-77baabe61c6c5ef8a7aea5687ed819ed5a0bb5b3%2Fk8s-deploy-satellite-3.png?alt=media" alt="k8s deploy satellite 3"><figcaption></figcaption></figure>
8. As soon as the Helm chart is generated, the cluster will be in **Pending** state, until the Satellite gets deployed and starts reporting to Prisma Cloud. It can take a few minutes for the Satellite to get successfully deployed.

   Once the deployment is complete, the cluster state will change to **Active**.

   Once a cluster is in the Active state, it sends keep-alives to Prisma Cloud every 30 minutes. If there is a communication issue or if the Satellite gets removed from the cluster, the object will move into an **Offline** state until the communication is re-established or the object is deleted on the Prisma Cloud console.

   <figure><img src="https://3990409212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyqPwsbMSaogAot23rTIu%2Fuploads%2Fgit-blob-a8b35312bb7fa777fae526bc65358b193dc31d9e%2Fk8s-deploy-satellite-4.png?alt=media" alt="k8s deploy satellite 4"><figcaption></figcaption></figure>

## Uninstall Satellite

To uninstall the Satellite operator:

1. Use the following command to uninstall Helm:

   `prismacloud-satellite -n pc-satellite`
2. Delete the cluster from the Satellite UI:

   On **Settings > K8s Satellite** select **Delete** under Actions for the corresponding cluster entry.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.prismacloud.io/content-collections/administration/network-security/container-network-exposure/deploy-satellite.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
