Skip to content

install: install and uninstall outside charts with the installer's Helm - #164

Closed
EItanya wants to merge 1 commit into
mainfrom
installer-helm-steps
Closed

EItanya wants to merge 1 commit into
mainfrom
installer-helm-steps

Conversation

@EItanya

@EItanya EItanya commented Nov 8, 2026

Copy link
Copy Markdown

kagent installs kagent and kagent-crds by running the helm binary. This adds HelmInstall and HelmUninstall, so kagent can use the installer's Helm client for them, with the same rules as the substrate releases:

kagent loads the chart itself, for example by pulling it from OCI with the Helm SDK.

The version mismatch error now says "upgrade it instead" rather than naming kubectl ate upgrade, since kagent shows it too.

I tested it on kind with a throwaway chart: install, reapply, refusing a newer chart version, and uninstall. There's no unit test, because the Helm client needs a cluster.

I wrote this with Claude Code and reviewed the diff.

kagent installs its own charts with the helm binary. Add HelmInstall and
HelmUninstall so it can install them with the same Helm client and rules
as the substrate releases, from a chart it loads itself. The version
mismatch error no longer names kubectl ate, since other programs show it.

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

EItanya commented Nov 9, 2026

Copy link
Copy Markdown
Author

Closing. This put substrate's release rules on kagent's charts and returned step closures. kagent already uses the Helm SDK for its OCI chart, so it can install, upgrade and uninstall its own releases with it directly and wrap those calls in install.Step.

Comment left by Claude on behalf of @EItanya

@EItanya EItanya closed this Nov 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant