kp_clusterbuilder_save.md

February 2, 2026 · View on GitHub

kp clusterbuilder save

Create or patch a cluster builder

Synopsis

Create or patch a cluster builder by providing command line arguments. The cluster builder will be created only if it does not exist, otherwise it is patched.

A buildpack order must be provided with either the path to an order yaml or via the --buildpack flag. Multiple buildpacks provided via the --buildpack flag will be added to the same order group.

Tag when not specified, defaults to a combination of the default repository and specified builder name. The default repository is read from the "default.repository" key in the "kp-config" ConfigMap within "kpack" namespace.

No defaults will be assumed for patches.

kp clusterbuilder save <name> [flags]

Examples

kp clusterbuilder save my-builder --order /path/to/order.yaml --stack tiny --store my-store
kp clusterbuilder save my-builder --buildpack my-buildpack-id --buildpack my-other-buildpack@1.0.1
kp clusterbuilder save my-builder --tag my-registry.com/my-builder-tag --order /path/to/order.yaml --stack tiny --store my-store
kp clusterbuilder save my-builder --tag my-registry.com/my-builder-tag --buildpack my-buildpack-id --buildpack my-other-buildpack@1.0.1

Options

  -b, --buildpack strings              buildpack id and optional version in the form of either '<buildpack>@<version>' or '<buildpack>'
                                         repeat for each buildpack in order, or supply once with comma-separated list
      --dry-run                        perform validation with no side-effects; no objects are sent to the server.
                                         The --dry-run flag can be used in combination with the --output flag to
                                         view the Kubernetes resource(s) without sending anything to the server.
  -h, --help                           help for save
  -o, --order string                   path to buildpack order yaml
      --order-from string              builder image to extract buildpack order from
      --output string                  print Kubernetes resources in the specified format; supported formats are: yaml, json.
                                         The output can be used with the "kubectl apply -f" command. To allow this, the command
                                         updates are redirected to stderr and only the Kubernetes resource(s) are written to stdout.
                                         The APIVersion of the outputted resources will always be the latest APIVersion known to kp (currently: v1alpha2).
      --registry-ca-cert-path string   add CA certificate for registry API (format: /tmp/ca.crt)
      --registry-verify-certs          set whether to verify server's certificate chain and host name (default true)
  -s, --stack string                   stack resource to use (default "default" for a create)
      --store string                   buildpack store to use
  -t, --tag string                     registry location where the builder will be created