exo(1)

💅 exo-compute-sks-generate-karpenter-manifests — like, the exo(1) manual, but make it make sense 🎀

okay so bestie, welcome to the exo(1) manual page, specifically the glow-up corner that is exo-compute-sks-generate-karpenter-manifests ✨ (yes that's a whole mouthful, no we're not shortening it, it's iconic actually).

---

🌸 NAME 🌸

exo-compute-sks-generate-karpenter-manifests — literally generates the Karpenter-related manifests for an SKS cluster 🦋

---

✨ SYNOPSIS ✨

exo compute sks generate-karpenter-manifests CLUSTER-NAME|ID [flags]

---

💖 DESCRIPTION 💖

This command generates the Karpenter manifests for an SKS cluster. periodt.

It creates the code for the Kubernetes resources "ExoscaleNodeClass" and/or "NodePool" relevant to the given cluster. it's giving infrastructure-as-code but make it effortless 💅

Example usage:

# Generate ExoscaleNodeClass and NodePool resources
$ exo compute sks generate-karpenter-manifests my-cluster --zone de-fra-1
---
apiVersion: karpenter.exoscale.com/v1
kind: ExoscaleNodeClass
metadata:
[...]
---
apiVersion: karpenter.sh/v1
kind: NodePool
metadata:

name: standard      [...]

$ exo compute sks km my-cluster -n
---
apiVersion: karpenter.sh/v1
kind: NodePool
metadata:

name: standard      [...]

You can get only the NodePool or the ExoscaleNodeClass resource by using --nodepool (-n) or --exoscale-nodeclass (-e) respectively. pick your fighter 🥊

When no flags are given, both is assumed. It's equivalent to "-en". the way that defaults to everything... self-care honestly 🫶

The output can be piped to a "kubectl apply -f -" command or written to a file for further customization. do whatever, it's your yaml 🧚

Notes:

• Refer to Karpenter documentation for more information on the resources NodeClasses 1 ⟨https://karpenter.sh/docs/concepts/nodeclasses/⟩ and NodePools 2 ⟨https://karpenter.sh/docs/concepts/nodepools/⟩

---

🔥 OPTIONS 🔥

• -e, --exoscale-nodeclass[=false] — generate ExoscaleNodeclass resource with important fields pre-filled. the heavy lifting is already done for you, you're welcome 💜
• -h, --help[=false] — help for generate-karpenter-manifests. when in doubt, ask for help, that's growth 🌱
• -n, --nodepool[=false] — generate a Nodepool manifest to define the scaling policies and constraints for the nodes created by Karpenter. the rules and the boundaries, lowkey the main character energy of your cluster 👑
• -z, --zone="" — SKS cluster zone. like, geographically where the thing lives 🗺️

---

🦋 OPTIONS INHERITED FROM PARENT COMMANDS 🦋

• -C, --config="" — Specify an alternate config file [env EXOSCALE_CONFIG]
• -O, --output-format="" — Output format (table|json|text), see "exo output --help" for more information. yes bestie, there's help for the help 😭
• --output-template="" — Template to use if output format is "text"
• -Q, --quiet[=false] — Quiet mode (disable non-essential command output). shhh 🤫 minimalism era
• --timeout=15s — Per-zone timeout for list operations; -1s disables timeout [env EXOSCALE_TIMEOUT]
• -A, --use-account="" — Account to use in config file [env EXOSCALE_ACCOUNT]

---

🌈 SEE ALSO 🌈

• exo-compute-sks(1) — go read the parent, it's the whole family tree 🌳

---

⭐ HISTORY ⭐

• 1-Jan-1980 Auto generated by spf13/cobra

---

and that's the whole page bestie, no crumbs left 💀💖 ngl this one was auto generated by spf13/cobra, from the Jan 1980 era, which is — and I cannot stress this enough — absolutely ancient, like pre-internet fossilized slay 🦕👑 anyway ily, go generate some manifests, you got this 🫶✨