exo(1)
πΈ exo(1) β the exo manual, bestie edition πΈ
okay so you opened exo(1) and you're like "what is this" β don't worry, I got you. this page is about one specific command, and it's lowkey the most niche little icon in the whole CLI. let's go π
β¨ NAME β¨
exo-compute-sks-nodepool-show β literally just Show an SKS cluster Nodepool details. that's the whole gig. she shows, you look. π
β¨ SYNOPSIS β¨
exo compute sks nodepool show CLUSTER-NAME|ID NODEPOOL-NAME|ID [flags]
so you pass a cluster β by name or by ID, your call, main character choice β and then a nodepool, again by name or ID. then flags if you're feeling fancy. periodt.
β¨ DESCRIPTION β¨
This command shows an SKS cluster Nodepool details. yes bestie that's genuinely it, it's a show command, it's giving "look but don't touch" β¨
okay and here's the part you actually need: you can template the output, and these are the supported output template annotations, copied exactly so you don't have to squint at a screenshot:
.ID, .Name, .Description, .CreationDate, .InstancePoolID, .InstancePrefix, .InstanceType, .Template, .DiskSize, .PublicIPAssignment, .IPv6, .AntiAffinityGroups, .SecurityGroups, .PrivateNetworks, .Version, .Size, .State, .Taints, .Labels, .NvidiaMigProfile, .AddOns, .ImageGCMin, .ImageGcLowThreshold, .ImageGcHighThreshold, .KubeletMaxPods
that's 25 annotations, and yes I listed every single one, because we do not skip. note that .ImageGCMin has a capital GC while .ImageGcLowThreshold and .ImageGcHighThreshold are Gc β that's not me being sloppy, that's literally how they're spelled, so run them exactly like that or the template will just vibe-check you into an error π
π OPTIONS π
-h,--help[=false]β help for show. default isfalse, but honestly if you're here, maybe flip it to true, no cap π«Ά-z,--zone=""β SKS cluster zone. defaults to empty string"". use it when you need to point at a specific zone.
π OPTIONS INHERITED FROM PARENT COMMANDS π
these aren't even her flags, she inherited them from the parent commands, and they still ate:
-C,--config=""β Specify an alternate config file. defaults to"".[env EXOSCALE_CONFIG]β yep, there's an env var for it π-O,--output-format=""β Output format (table|json|text), see"exo output --help"for more information. defaults to"". pick your aesthetic β¨--output-template=""β Template to use if output format is"text". defaults to"". this is where those annotations above come in, iykyk π¦-Q,--quiet[=false]β Quiet mode (disable non-essential command output). defaultfalse. for when you want her to whisper π€«--timeout=15sβ Per-zone timeout for list operations;-1sdisables timeout.[env EXOSCALE_TIMEOUT]. default is15s, and fun fact:-1sturns the timeout off entirely, which is a real thing you can do, so. be mindful π-A,--use-account=""β Account to use in config file. defaults to"".[env EXOSCALE_ACCOUNT]πΈ
β SEE ALSO β
exo-compute-sks-nodepool(1)β go read that one next, she's the parent and she has lore π§
π HISTORY π
1-Jan-1980 Auto generated by spf13/cobra
yes. 1980. auto generated. the origin story is literally just cobra doing its thing and honestly? iconic π
and that's the page!! π this whole thing β every word of it β was Auto generated by spf13/cobra, and the version/date stamp down in the footer says Jan 1980. so like, she's auto-generated and she's vintage. a legend, fr fr π«Άβ¨
π¦ where this page comes from
- nixpkgs unstable: exoscale-cli 1.102.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms