
hull
Write, check and convert Helm charts built with the HULL library: a skill with the rules of HULL and an MCP server that validates, renders and imports charts and looks up the schema.
- GitHub stars
- 295
Install
/plugin install hull@vidispine-hullRun it inside Claude Code after adding the marketplace with /plugin marketplace add vidispine/hull.
Contents
Discovered from sourceSkills 1
Working with HULL charts
A HULL chart has a single template, templates/hull.yaml, and defines every Kubernetes object as data in values.yaml under hull.objects.<type>.<key>. The values are validated by the JSON schema of the chart's HULL dependency. Do not write Go templates for objects.
The rules below describe HULL 1.35.5, 1.36.2, 1.37.1 and later. Older versions lack some features, for example image digests and explicit selectors; hull_docs with the chart's directory as chart_dir returns the documentation of the chart's own HULL version.
Workflow
Use the hull MCP tools when they are available:
- Before writing values, read the rules once:
hull_docswith topicguide. For common tasks start from a tested recipe:hull_docswith topiccookbook. - Look up what is allowed instead of guessing:
hull_schemawith a values path such ashull.objects.deployment.web.pod.containers.main, an object type or a definition name. - After every change run
hull_validateon the chart and fix every reported problem. Each problem is one line:HULL failed with error [CODE] (@Values.<path>) <message> Fix: <hint>. For details about a code usehull_docswith the code as topic. - Inspect the result with
hull_render, usingkindandnameto select objects. - To convert an existing chart, render it with
helm template <release> <chart> --namespace <ns>and pass the output tohull_importwith the same release name and namespace. It writes a HULL chart and verifies that it renders the same objects. Then refactor the verified values into idiomatic HULL in small steps and compare the rendering after each step.
Without the MCP tools, the same is available as scripts in the HULL chart, in files/scripts of the dependency (unpack it with tar -xzf charts/hull-*.tgz -C /tmp): python3 hull_validate.py <chart>, python3 hull_import.py --chart <dir> --verify <manifests>, and the documentation in files/doc, starting with agents.md and cookbook.md.
Rules that differ from Kubernetes YAML
- The instance key is the name:
hull.objects.deployment.webrenders<release>-<chart>-web.staticName: trueorhull.config.general.noObjectNamePrefixes: truekeep the key unchanged. - Write the fields of
specdirectly below the instance key, withoutspec:. Pod based objects take the pod spec inpod, CronJobs injob.pod. Pod labels and annotations go topod.labelsandpod.annotations. - Named arrays are dictionaries keyed by name:
containers,initContainers,volumes,env,ports. Never addname:to them.volumeMounts,envFrom, Ingressrules,paths,tlsandwebhooksare dictionaries with free keys. Elements render in key order, use an integerorderproperty where order matters. - Images:
image: {registry, repository, tag, digest}; a non-empty digest replaces the tag. Quote tags like"1.10". - Selectors are generated from chart, release and key. A Service without
selectorselects the pods of the workload with the same key. An explicitselectorkeeps an existing selector; the pod labels must then match it. - References to chart objects use the key and get the name prefix: configMap/secret/PVC volumes, env and envFrom refs, Ingress backends and TLS secrets, HPA targets. Add
staticName: truenext to a name that refers to an object outside the chart.serviceAccountName,imagePullSecretsand RoleBinding names are rendered as written; use_HT^<key>for the full name of a chart object. - ConfigMap and Secret data:
data.<key>.inlineordata.<key>.path. Secret values are plain text, HULL encodes them. AddnoTemplating: trueto content containing{{. - Defaults:
_HULL_OBJECT_TYPE_DEFAULT_instances or elements, and namedsources. - The
defaultServiceAccount, Role and RoleBinding: since HULL 1.37 they only exist withhull.config.general.createDefaultRbacTriplet: true. Up to 1.36 they are rendered for every release and pods withoutserviceAccountNameget thedefaultServiceAccount; setenabled: falseon them to leave them out. - Kinds without a HULL object type are
genericobjects withapiVersion,kindand their fields.
Transformations
Strings starting with these prefixes are computed:
| Prefix | Result |
|---|---|
_HT*hull.config.specific.x | the value at the path below .Values |
_HT**Release.Name | the same from the root context |
_HT!{{ ... }} | a Go template result; (index . "$") is the root context |
_HT?<condition> | a boolean, for enabled |
_HT^<key> | the full name of a chart object |
_HT&<key> | the generated selector labels of a key |
Keep shared values in hull.config.specific and reference them with _HT*. Write lists and dictionaries returned by _HT! in flow style, with embedded references inside {{ }}: _HT![ {{ _HT*hull.config.specific.host }} ]. Transformations are not applied to single list elements: a transformation as first element replaces the whole list, later elements stay literal.
MCP servers 1
Sponsors
Details
- Marketplace
- vidispine/hull
- Source
- hull/files/scripts
- Category
- Community