`maqpna console`

Open the console of an installation

Synopsis#

maqpna console [--port 8088] [--open] [--gateway URL | --operator-namespace NS [--service NAME]]

Description#

Serves the embedded web console on 127.0.0.1 and proxies the gateway admin API on the same origin, so the gateway needs no corsOrigins entry. Without --gateway it runs kubectl port-forward to the gateway Service (the admin listener when the chart exposes one). -o json prints the addresses once.

Flags#

Flag	Type	Description	Default
`--gateway`	string	reach the gateway at this URL instead of port-forwarding to the cluster	none
`--open`	switch	open the console in the browser	none
`--operator-namespace`	string	namespace of the gateway Service	`maqpna-system`
`--port`	int	local port of the console (0: any free port)	`8088`
`--service`	string	gateway Service name (default: found by label app.kubernetes.io/component=gateway)	none

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

Examples#

$ maqpna console --open
$ maqpna console --gateway https://gateway.example.eu

What happens when you run it#

Talks to the gateway: --gateway, else MAQPNA_GATEWAY_URL, else the current context's gateway (maqpna context).
Prints a table by default; -o json or -o yaml print the data, and --jq EXPR filters the JSON.

Exit codes#

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

Terminal demo#

maqpna console --help.cast

This command needs a Kubernetes cluster with MAQPNA installed, so the recording shows its help. Try it against a cluster from Install.