KRAFT-CLOUD-INSTANCE-CREATE(1)

💅 kraft-cloud-instance-create — NAME

okay so bestie, this is kraft-cloud-instance-create and it does exactly one iconic thing: create an instance. that's it, that's the vibe. 👑

---

✨ SYNOPSIS ✨

kraft cloud instance create [FLAGS] IMAGE [-- ARGS]

---

🦋 DESCRIPTION 🦋

You're creating an instance on Unikraft Cloud, starting from an image. That's the whole plot. Image in, instance out, main character energy fr fr. 💖

---

🎀 OPTIONS 🎀

so many flags, but every single one is serving a purpose, no cap:

• -c, --certificate=[] — the certificates you wanna use for the service
• -d, --domain=[] — the domain names to use for the service
• --entrypoint=[] — set the entrypoint for the instance
• -e, --env=[] — environmental variables
• -f, --feature=[] — list of features to enable
• -h, --help[=false] — help for create
• -M, --memory="" — specify the amount of memory to allocate (MiB increments)
• -n, --name="" — specify the name of the instance
• -o, --output="list" — set output format. Options: table,yaml,json,list,raw
• -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)
• --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 this instance to an existing service
• -S, --start[=false] — immediately start the instance after creation
• -s, --subdomain=[] — set the subdomains to use when creating the service
• -V, --vcpus=0 — specify the number of vCPUs to allocate
• -v, --volume=[] — list of volumes to attach instance to

---

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

the nepo babies of the flag world, but make it useful 🫶:

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

---

🔥 EXAMPLES 🔥

💜 example one — nginx, but make it live

create a new NGINX instance and start it immediately. map the external port 443 to the internal port 8080 which the application listens on.

$ kraft cloud instance create \
          --start \
          --port 443:8080 \
          nginx:latest

🍓 example two — the elaborate port expression

this command is the same as above, however using the more elaborate port expression. this is because in fact we need need to accept TLS and HTTP connections and redirect port 8080 to port 443. the above example exists only as a shortcut for what is written below:

$ kraft cloud instance create \
          --start \
          --port 443:8080/http+tls \
          --port 80:443/http+redirect \
          nginx:latest

not me pointing out that the original says "need need" — yes bestie, i said it twice too, that's how much we need it 😭

🧚 example three — volumes, plural, obsessed

attach two existing volumes to the vm, one read-write at /data and another read-only at /config:

$ kraft cloud instance create \
          --start \
          --volume my-data-vol:/data \
          --volume my-config-vol:/config:ro \
          nginx:latest

---

⭐ SEE ALSO ⭐

• kraft-cloud-instance(1) — go read that one next, iykyk

---

🌸 HISTORY 🌸

1-Jan-1980 — Auto generated by KraftKit. yes, 1980. she's vintage. absolute icon behavior. 💀✨

---

and that's the whole page bestie!! rendered from the KraftKit Documentation, dated Jan 1980, and living under the KraftKit CLI(1) banner — go forth and create instances, you gorgeous genius 🎀💅🦋