> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-0-3/documentation/agents/agents-in-kubernetes/remote-agents-with-the-connectware-agent-helm-chart.md).

# Remote Agents with the connectware-agent Helm Chart

Remote agents are Connectware agents that are not directly integrated into the Connectware installation, but standalone deployments that are managed separately.

A common use case for remote agents is using a target infrastructure that is closer to the shop floor than the Connectware installation, but from a Kubernetes point of view they can also be deployed in the same namespace.

Cybus offers a Helm chart to comfortably deploy remote agents.

Please review the requirements for your Kubernetes cluster in Kubernetes cluster requirements for the connectware-agent Helm chart before proceeding with Installing Connectware agents using the connectware-agent Helm chart or Installing Connectware agents without a license key using the connectware-agent Helm chart.

**Related Links**

* Upgrading the connectware-agent Helm chart
* Uninstalling Connectware agents with the connectware-agent Helm chart
* Configuration principles for the connectware-agent Helm chart
* Configuring agents with the connectware-agent Helm chart
* Troubleshooting agents installed with the connectware-agent Helm chart


---

# 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.cybus.io/2-0-3/documentation/agents/agents-in-kubernetes/remote-agents-with-the-connectware-agent-helm-chart.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.