mait.sh1.132.1

Private beta: features and content may change. No warranty; use at your own risk.

Use cases

Six things you ask your agent to do with charts and releases, from checking a chart to removing a release and its history.

Beta
Inspect releases

What is running in this namespace?

You want to know which releases a namespace holds and what each one is on, before anyone changes it.

Illustrative conversation
YouShow me the releases in the demo namespace and the history of demo-release.
Tool callhelm_release { "action": "list", "namespace": "demo" }
What happensOne release, demo-release, with its stored revisions and status Deployed.
Tool callhelm_release { "action": "history", "name": "demo-release", "namespace": "demo" }
What happensEach revision with its status, chart, chart version and info.
Agentdemo-release is at revision 1, Deployed, chart minimal-chart 0.1.0. That is the record; I would check its resources to confirm they are healthy.
Check a chart

Check a chart before installing it

You have a chart and want to know whether it will install, before it touches the cluster.

Illustrative conversation
YouLint this chart and show me what it would create in the web namespace.
Tool callhelm_chart { "action": "lint", "chart_path": "/charts/minimal-chart" }
What happensThe result is status valid, with a short message.
Tool callhelm_template { "action": "render", "chart_source": "/charts/minimal-chart", "release_name": "demo", "namespace": "web" }
What happensOne manifest comes back, a ConfigMap named demo-sample in the web namespace, with its source comment.
AgentThe chart renders to one ConfigMap and nothing is left unresolved. It fits what this server can install.
Install

Install a chart and check the result

The chart looks right and you want it running as a release.

Illustrative conversation
YouInstall this chart as demo in the web namespace.
Tool callhelm_release { "action": "install", "name": "demo", "namespace": "web", "chart": "/charts/minimal-chart" }
What happensThe result is name demo, namespace web, version 1, status Deployed.
Tool callhelm_release { "action": "status", "name": "demo", "namespace": "web" }
What happensThe latest recorded status is Deployed.
Agentdemo is installed at revision 1. That is the record; I will read its ConfigMap with kubectl to confirm the resource really exists.
Upgrade and roll back

Upgrade, and go back if it is wrong

A new chart version is ready, and you want a way back if it misbehaves.

Illustrative conversation
YouUpgrade demo to the new chart and roll back if the data is wrong.
Tool callhelm_release { "action": "upgrade", "name": "demo", "namespace": "web", "chart": "/charts/minimal-chart" }
What happensThe result is a new revision, 2, with status Deployed.
AgentRevision 2 is deployed, but the ConfigMap still shows the old value, so I am rolling back to revision 1.
Tool callhelm_release { "action": "rollback", "name": "demo", "namespace": "web", "revision": 1 }
What happensA new revision, 3, is written from revision 1's chart and values.
Agentdemo is back on the revision 1 chart as revision 3. Resources that revision 2 added, if any, are not removed; I will check for those.
Find a chart

Find a chart and pull it

You are looking for a chart in a repository your team approved, and you want it on disk to review.

Illustrative conversation
YouAdd our chart repository, find the chart called minimal and download version 1.2.3.
Tool callhelm_repository { "action": "add", "name": "approved", "url": "https://charts.example.com" }
What happensThe registration is saved and its index is fetched.
Tool callhelm_repository { "action": "search", "query": "minimal", "max_results": 20 }
What happensThe matching charts, with their versions and descriptions.
Tool callhelm_chart { "action": "pull", "repository": "approved", "chart": "minimal", "version": "1.2.3", "destination": "/downloads" }
What happensThe result names the downloaded file.
Tool callhelm_chart { "action": "show", "source": "/downloads/minimal-1.2.3.tgz" }
What happensThe chart's name, version, description and dependencies.
AgentThe archive is a chart named minimal at 1.2.3. I read its metadata; its templates still need a look before an install.
Remove

Remove a release, and decide about its history

The release is done and you want it gone, keeping its record only if you may need it.

Illustrative conversation
YouUninstall demo, but keep its history until I have checked.
Tool callhelm_release { "action": "uninstall", "name": "demo", "namespace": "web", "keep_history": true }
What happensThe delete requests are accepted; the records stay and the latest revision reads Uninstalled.
Agentdemo is uninstalled and its history is kept. I will check the resources and tell you when they are gone; the name stays taken until the history is removed.