v0.2.1

What's Changed

• fix(helm): Add /tmp volume and volumeMount to tools deployment by @jmhbh in #61

New Contributors

• @jmhbh made their first contribution in #61

Full Changelog: v0.2.0...v0.2.1

v0.2.0

refactor(helm): remove rbac.clusterScoped, derive RBAC scope from rba…

v0.1.4

Fix incorrect cillium-dbg subcommands (#55)

Signed-off-by: Dmytro Rashko <dmitriy.rashko@amdocs.com>

* Fix incorrect cilium-dbg subcommands
* Bump outdated tools:
- Argo Rollouts: 1.8.4 → 1.9.0
- Istio: 1.28.5 → 1.29.1

v0.1.3

feat(helm): support namespaced RBAC for tools (#53)

* namespaced rbac

Signed-off-by: Jet Chiang <pokyuen.jetchiang-ext@solo.io>

* oops forgot i renamed it

Signed-off-by: Jet Chiang <pokyuen.jetchiang-ext@solo.io>

---------

Signed-off-by: Jet Chiang <pokyuen.jetchiang-ext@solo.io>

v0.1.2

fix(security): bump grpc and CLI tool versions to resolve CVEs (#52)

Bump google.golang.org/grpc v1.78.0 -> v1.79.3 to fix CRITICAL
CVE-2026-33186 (authorization bypass). Bump all bundled CLI tools
to latest releases (kubectl 1.35.3, helm 4.1.3, istioctl 1.28.5,
argo-rollouts 1.8.4, cilium 0.19.2) to reduce CVE surface area.

Signed-off-by: Eitan Yarmush <eitan.yarmush@solo.io>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

v0.1.1

fix(helm): rename helpers to avoid parent chart collision (#49)

Renames all helper templates from kagent.* to kagent-tools.* prefix to
prevent naming conflicts with the parent kagent chart. When Helm renders
subcharts, template definitions are global, causing the parent chart's
helpers to override the subchart's helpers with the same names.

This fixes:
- Selector label mismatch when using nameOverride (was using parent's
  logic instead of subchart's fullname logic)
- Helm upgrade failures due to immutable selector field changes
- Enables proper use of nameOverride instead of requiring
  fullnameOverride workaround

All helper references updated across all template files:
- _helpers.tpl: Renamed 10 helper definitions
- deployment.yaml, service.yaml, serviceaccount.yaml: Updated references
- clusterrole.yaml, clusterrolebinding.yaml: Updated references
- servicemonitor.yaml, NOTES.txt: Updated references

Backward compatible: existing fullnameOverride usage continues to work.

Signed-off-by: Eitan Yarmush <eitan.yarmush@solo.io>
Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>

v0.1.0

fix(helm): use fullname in selector labels to prevent mismatch on upg…

v0.0.16

What's Changed

• feat(helm): configurable RBAC with read-only ClusterRole support by @MatteoMori8 in #46

Full Changelog: v0.0.15...v0.0.16

v0.0.15

feat: add token support for kubectl commands (#37)

* feat: add token support for kubectl commands

Signed-off-by: Eitan Yarmush <eitan.yarmush@solo.io>

* use pre-v4 helm version

Signed-off-by: Eitan Yarmush <eitan.yarmush@solo.io>

* Add configuration to disable service token automount

Signed-off-by: Jeremy Alvis <jeremy.alvis@solo.io>

* Remove automountServiceAccountToken config

Signed-off-by: Jeremy Alvis <jeremy.alvis@solo.io>

* helm config for using default service account

Signed-off-by: Jeremy Alvis <jeremy.alvis@solo.io>

* Add tools.k8s.tokenPassthrough for requiring token from auth header

Signed-off-by: Jeremy Alvis <jeremy.alvis@solo.io>

* Fix helm version

Signed-off-by: Jeremy Alvis <jeremy.alvis@solo.io>

* Remove automountServiceAccountToken from helm test

Signed-off-by: Jeremy Alvis <jeremy.alvis@solo.io>

* Redact tokens

Signed-off-by: Jeremy Alvis <jeremy.alvis@solo.io>

---------

Signed-off-by: Eitan Yarmush <eitan.yarmush@solo.io>
Signed-off-by: Jeremy Alvis <jeremy.alvis@solo.io>
Co-authored-by: Jeremy Alvis <jeremy.alvis@solo.io>

v0.0.14

feat(cli): add --read-only flag to disable write operations (#41)

* feat: add --read-only flag to disable write operations

Add a new `--read-only` CLI flag that disables tools which perform
write operations (delete, patch, scale, create, apply, etc.).

This enables deploying the MCP server in read-only mode for:
- Observability-only use cases (monitoring, troubleshooting)
- Environments with read-only service accounts
- Compliance requirements separating read/write capabilities

Tools are categorized as read-only or write operations:
- K8s: 8 read-only, 14 write tools
- Helm: 3 read-only, 3 write tools
- Istio: 9 read-only, 3 write tools
- Cilium: ~25 read-only, ~15 write tools
- Argo: 4 read-only, 4 write tools
- Prometheus/Kubescape/Utils: all read-only (unchanged)

Co-Authored-By: Claude Opus 4.5
Signed-off-by: Matteo Mori <matteo.mori@rvu.co.uk>

* fix: disable shell tool in read-only mode

The utils provider exposes a `shell` tool that executes arbitrary
commands, bypassing read-only restrictions. In read-only mode, this
tool is now disabled.

Also pass readOnly to all providers (kubescape, prometheus, utils)
for consistency with the existing providers.

Signed-off-by: Matteo Mori <matteo.mori@rvu.co.uk>

---------

Signed-off-by: Matteo Mori <matteo.mori@rvu.co.uk>