kp_clusterbuilder_patch.md

February 2, 2026 ยท View on GitHub

kp clusterbuilder patch

Patch an existing cluster builder configuration

Synopsis

Patch an existing clusterbuilder configuration by providing command line arguments.

A buildpack order must be provided with either the path to an order yaml, via the --buildpack flag, or extracted from a builder image using --order-from. Multiple buildpacks provided via the --buildpack flag will be added to the same order group.

kp clusterbuilder patch <name> [flags]

Examples

kp clusterbuilder patch my-builder --order /path/to/order.yaml --stack tiny --store my-store
kp clusterbuilder patch my-builder --order /path/to/order.yaml
kp clusterbuilder patch my-builder --order-from paketobuildpacks/builder-jammy-base
kp clusterbuilder patch my-builder --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 patch
  -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
      --store string                   buildpack store to use
  -t, --tag string                     registry location where the builder will be created

SEE ALSO