|
| 1 | +## kp clusterlifecycle save |
| 2 | + |
| 3 | +Create or patch a cluster lifecycle |
| 4 | + |
| 5 | +### Synopsis |
| 6 | + |
| 7 | +Create or patch a cluster-scoped lifecycle by providing command line arguments. |
| 8 | + |
| 9 | +The image will be uploaded to the default repository. |
| 10 | +Therefore, you must have credentials to access the registry on your machine. |
| 11 | +Additionally, your cluster must have read access to the registry. |
| 12 | + |
| 13 | +Env vars can be used for registry auth as described in https://github.com/buildpacks-community/kpack-cli/blob/main/docs/auth.md |
| 14 | + |
| 15 | +The default repository is read from the "default.repository" key in the "kp-config" ConfigMap within "kpack" namespace. |
| 16 | +The default service account used is read from the "default.repository.serviceaccount" key in the "kp-config" ConfigMap within "kpack" namespace. |
| 17 | + |
| 18 | + |
| 19 | +``` |
| 20 | +kp clusterlifecycle save <name> [flags] |
| 21 | +``` |
| 22 | + |
| 23 | +### Examples |
| 24 | + |
| 25 | +``` |
| 26 | +kp clusterlifecycle save my-lifecycle --image buildpacksio/lifecycle |
| 27 | +``` |
| 28 | + |
| 29 | +### Options |
| 30 | + |
| 31 | +``` |
| 32 | + --dry-run perform validation with no side-effects; no objects are sent to the server. |
| 33 | + The --dry-run flag can be used in combination with the --output flag to |
| 34 | + view the Kubernetes resource(s) without sending anything to the server. |
| 35 | + --dry-run-with-image-upload similar to --dry-run, but with container image uploads allowed. |
| 36 | + This flag is provided as a convenience for kp commands that can output Kubernetes |
| 37 | + resource with generated container image references. A "kubectl apply -f" of the |
| 38 | + resource from --output without image uploads will result in a reconcile failure. |
| 39 | + -h, --help help for save |
| 40 | + -i, --image string image tag or local tar file path |
| 41 | + --output string print Kubernetes resources in the specified format; supported formats are: yaml, json. |
| 42 | + The output can be used with the "kubectl apply -f" command. To allow this, the command |
| 43 | + updates are redirected to stderr and only the Kubernetes resource(s) are written to stdout. |
| 44 | + The APIVersion of the outputted resources will always be the latest APIVersion known to kp (currently: v1alpha2). |
| 45 | + --registry-ca-cert-path string add CA certificate for registry API (format: /tmp/ca.crt) |
| 46 | + --registry-verify-certs set whether to verify server's certificate chain and host name (default true) |
| 47 | +``` |
| 48 | + |
| 49 | +### SEE ALSO |
| 50 | + |
| 51 | +* [kp clusterlifecycle](kp_clusterlifecycle.md) - ClusterLifecycle Commands |
| 52 | + |
0 commit comments