> For the complete documentation index, see [llms.txt](https://docs.lenses.io/latest/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lenses.io/latest/changelog/lenses-6.3/helm.md).

# Helm Chart

Helm chart change log for Lenses 6.3.

Chart versions published on the `release/6.3` branch of [lenses-helm-charts](https://github.com/lensesio-dev/lenses-helm-charts). Entries are derived from the chart `version:` bumps and the corresponding commit messages.

{% updates format="full" %}
{% update date="2026-10-09" tags="improvements" %}

## HQ 6.3.0 · Agent 6.3.0

* Agent: the Role and ClusterRole no longer grant access the Agent does not use (persistent volumes and claims, ingresses, and creating namespaces), and list each resource under the API group that serves it.
* HQ: the Role and ClusterRole no longer grant `ingresses` and `routes`. HQ makes no Kubernetes API calls.
* HQ: new `serviceAccount.automountToken` value (default `true`). Set it to `false` to stop mounting a service account token into the HQ pod and the MCP sidecar.
* Both charts fail with a clear message when `serviceAccount.create` is `true` and `serviceAccount.name` is `default`, a combination that cannot work.
* No default values change. The MCP sidecar keeps image tag 6.2.2.
  {% endupdate %}
  {% endupdates %}


---

# 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.lenses.io/latest/changelog/lenses-6.3/helm.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.