KRAFT-CLOUD-DEPLOY(1)

🎀 KRAFT-CLOUD-DEPLOY(1) 🎀

okay so this page is from the KraftKit Manual and lives under the KraftKit CLI, bestie. This is kraft-cloud-deploy, and it's giving one-command deploy realness. The whole vibe: build, package, ship, and deploy without bouncing between a million sub-commands. Obsessed.

---

✨ NAME ✨

kraft-cloud-deploy — deploy your application. periodt.

🛠️ SYNOPSIS 🛠️

kraft cloud deploy [ARGS] [CONTEXT] [-- [APP ARGS]]

💖 DESCRIPTION 💖

kraft cloud deploy is literally the combo move: it combines a number of kraft cloud sub-commands so you can build, package, ship, and deploy your application with a single command. No cap, that's the whole flex.

🌈 OPTIONS 🌈

• -D, --as="" — set the deployment type
• --build-log="" — use the specified file to save the output from the build
• -C, --certificate=[] — set the certificates to use for the service
• -z, --compress[=false] — compress the initrd package (experimental — yes, the original says so 🧪)
• -c, --config="" — override the path to the KConfig .config file
• --dbg[=false] — build the debuggable (symbolic) kernel image instead of the stripped image
• -d, --domain=[] — set the domain names for the service
• --entrypoint=[] — set the entrypoint for the instance
• -e, --env=[] — environmental variables
• --feature=[] — specify the special features to enable
• -f, --follow[=false] — follow the logs of the instance
• --force-pull[=false] — force pulling packages before building
• -h, --help[=false] — help for deploy (the classic rescue button 🫶)
• -i, --image="" — set the image name to use
• -j, --jobs=0 — allow N jobs at once
• --keep-file-owners[=false] — keep file owners (user:group) in the rootfs (false sets 'root:root')
• -K, --kraftfile="" — set the Kraftfile to use
• -M, --memory="" — specify the amount of memory to allocate (MiB increments)
• -n, --name="" — name of the deployment
• -F, --no-cache[=false] — force a rebuild even if existing intermediate artifacts already exist
• --no-configure[=false] — do not run Unikraft's configure step before building
• --no-fast[=false] — do not use maximum parallelization when performing the build
• --no-fetch[=false] — do not run Unikraft's fetch step before building
• -S, --no-start[=false] — do not start the instance after creation
• --no-update[=false] — do not update package index before running the build
• -o, --output="" — set output format
• -p, --port=[] — specify the port mapping between external to internal
• -R, --replicas=0 — number of replicas of the instance
• --restart="never" — set the restart policy for the instance (never/always/on-failure)
• --rollout="prompt" — set the rollout strategy for an instance which has been previously run in the provided service.
• --rollout-qualifier="image" — set the rollout qualifier used to determine which instances should be affected by the strategy in the supplied service.
• --rollout-wait=10s — time to wait before performing rolling out action (ms/s/m/h)
• --rootfs="" — specify a path to use as root filesystem
• --rootfs-type="cpio" — set the type of the format of the rootfs (cpio/erofs)
• --runtime="" — set an alternative project runtime
• --scale-to-zero="off" — scale to zero policy of the instance (on/off/idle)
• --scale-to-zero-cooldown=0s — cooldown period before scaling to zero (ms/s/m/h)
• --scale-to-zero-stateful[=false] — save state when scaling to zero
• -g, --service="" — attach the new deployment to an existing service
• --strategy="overwrite" — when a package of the same name exists, use this strategy when applying targets.
• -s, --subdomain=[] — set the names to use when provisioning subdomains
• --timeout=1m0s — set the timeout for remote procedure calls (ms/s/m/h)
• -V, --vcpus=0 — specify the number of vCPUs to allocate
• -v, --volume=[] — specify the volume mapping(s) in the form NAME:DEST or NAME:DEST:OPTIONS
• -w, --workdir="" — set an alternative working directory (default is cwd)

🧚 OPTIONS INHERITED FROM PARENT COMMANDS 🧚

these come from the parent command, bestie — not me making stuff up:

• --allow-insecure[=false] — allow insecure connections to the Unikraft Cloud API
• --metro="" — Unikraft Cloud metro location
• --token="" — Unikraft Cloud access token

🍓 EXAMPLES 🍓

the receipts, fr fr:

# Deploy a working directory with a Kraftfile or Dockerfile:
$ kraft cloud deploy -p 443:8080

# Run an image from Unikraft Cloud's image catalog:
$ kraft cloud deploy -p 443:8080 caddy:latest

# Supply arguments to the instance of the existing image
$ kraft cloud deploy -p 443:8080 caddy:latest -- /bin/server --debug

# Supply arguments to the instance of the project (appending to the cmd):
$ kraft cloud deploy -p 443:8080 . -- /bin/server --debug

# Supply arguments to the instance of the project (overwriting the cmd):
$ kraft cloud deploy -p 443:8080 --entrypoint "/bin/server --debug" .

# Immediately start following the log tail
$ kraft cloud deploy -p 443:8080 -f caddy:latest

🦋 SEE ALSO 🦋

go be nosy: kraft-cloud(1)

⭐ HISTORY ⭐

1-Jan-1980 — Auto generated by KraftKit

---

💌 cute little sign-off: source/version is KraftKit Documentation, date is Jan 1980, manual is KraftKit CLI(1). mwah 🫶✨