MAQPNADocs

maqpna api-resources

List the resource types maqpna knows, with short names (kubectl api-resources)

Get started-o json | yaml

Synopsis#

maqpna api-resources [--namespaced=true|false] [--api-group G] [--source kube|gateway] [--sort-by name|kind] [--no-headers] [-o wide|name|json|yaml]

Description#

The maqpna.com kinds come from the CRDs this CLI was built with (their short names and the "maqpna" category work in kubectl too: kubectl get ag, kubectl get maqpna). The gateway's runtime kinds (APIVERSION gateway/v1) are served by the gateway admin API; maqpna get and describe read them, kubectl cannot. ALIASES (-o wide) are names only this CLI accepts.

Flags#

FlagTypeDescriptionDefault
--api-groupstringonly this API group (maqpna.com, gateway)none
--cachedswitchignored (maqpna reads its built-in CRDs)none
--namespacedstringtrue: namespaced types only; false: cluster-scoped onlynone
--no-headersswitchomit the header rownone
--sort-bystringname | kindnone
--sourcestringkube | gatewaynone
--verbsstringonly types supporting these verbsnone

The global flags (--context, -o, --no-color, ...) work with every command.

Examples#

maqpna api-resources
maqpna api-resources -o wide
maqpna api-resources --namespaced=false -o name

What happens when you run it#

  • Prints a table by default; -o json or -o yaml print the data, and --jq EXPR filters the JSON.

Exit codes#

CodeMeaning
0success
1error (the message says what failed, with a hint when there is one)
2usage error: unknown flag, missing argument or bad value; the synopsis is printed
3a check failed, a change is blocked, or a result did not match (tamper, policy mismatch) (not used by this command)