hull create

hull create scaffolds a ready-to-edit hull package — a working Deployment + Service with values already wired in — in a new directory.

When to use it

  • You want a working starter you can render and edit immediately, not a menu of layouts.
  • You want the batteries-included set: a helpers partial, notes, and a .hullignore already in place.
  • For a choice of workload shapes (webapp, batch, operator, blank) use hull init instead.

What happens

  1. Creates a directory named after <name> (fails if it already exists).
  2. Writes hull.yaml (name, version, description) and a values.yaml seeded with replicaCount, image, and service.port.
  3. Writes a templates/ directory: deployment.yaml, service.yaml, a _helpers.yaml partial, and notes.yaml.
  4. Writes a .hullignore listing patterns to skip when packaging.
  5. Prints created package <name>/.

The templates read the seeded values via ${values.*}, so the package renders and lints as-is. Edit the files, then run hull lint and hull template.

Usage 

hull create <name> [flags]

Flags

Inherits the global flags.

Worked example

Scaffold a package called myapp:

hull create myapp

OUTPUT:

created package myapp/

What you now have on disk:

myapp/
├── .hullignore
├── hull.yaml
├── values.yaml
└── templates/
    ├── _helpers.yaml
    ├── deployment.yaml
    ├── notes.yaml
    └── service.yaml

values.yaml sets replicaCount: 1, image.repository: nginx, and service.port: 80, and the templates reference those values, so the package renders straight away:

cd myapp
hull template .

Change replicaCount or the image in values.yaml and re-render to watch the manifest update.

See also

  • init — scaffold from a chosen built-in template
  • lint — validate the scaffolded package
  • template — render it to manifests
  • values — how values files and --set overrides merge