> 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-6-1/cybus-helm-charts/connectware-toolkit-helm-chart/sharing-connectware-certificates-with-the-toolkit-container.md).

# Sharing Connectware Certificates with the Toolkit Container

Mount the Connectware certs volume into the toolkit container to give it access to the certificates used by Connectware components.

Connectware components use certificates to authenticate and secure their communication. Mounting the Connectware certs volume into the toolkit container gives the toolkit access to those certificates. This is most commonly used when debugging Connectware components.

## Configuration

How you enable the certs volume depends on how you installed the `connectware-toolkit` chart.

{% tabs %}
{% tab title="connectware Helm Chart" %}
When you deploy the toolkit as a subchart of the `connectware` Helm chart, the certs volume is mounted by default once the toolkit is enabled:

{% code title="values.yaml" lineNumbers="true" %}

```yaml
toolkit:
  enabled: true
  # mountCertsVolume defaults to true
```

{% endcode %}

To opt out of mounting the certs volume, set `toolkit.mountCertsVolume` to `false`:

{% code title="values.yaml" lineNumbers="true" %}

```yaml
toolkit:
  enabled: true
  mountCertsVolume: false
```

{% endcode %}
{% endtab %}

{% tab title="connectware-toolkit Helm Chart" %}
When you deploy the toolkit as a standalone Helm installation, the `connectware-toolkit` chart must be installed in the same namespace as the `connectware` chart. Set `mountCertsVolume: true` to mount the Connectware certs volume:

{% code title="values.yaml" lineNumbers="true" %}

```yaml
mountCertsVolume: true
```

{% endcode %}
{% endtab %}
{% endtabs %}


---

# 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-6-1/cybus-helm-charts/connectware-toolkit-helm-chart/sharing-connectware-certificates-with-the-toolkit-container.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.