maqpna install
Install MAQPNA in a cluster with Helm
Synopsis#
maqpna install [--profile dev|prod|sovereign-eu] [-f values.yaml] [--set K=V] [--chart oci://...|DIR] [--version V]
[--release maqpna] [-n maqpna-system] [--dry-run] [--wait] [--timeout 10m] [--skip-crds]Description#
The chart defaults to oci://<release-registry>/charts/maqpna at this CLI's version. --profile selects a values file shipped with the chart (values-dev.yaml, values-production.yaml, values-sovereign-eu.yaml); -f and --set override it. Run 'maqpna preflight' with the same flags first. --dry-run renders on the API server (lookups included) and changes nothing.
Flags#
| Flag | Type | Description | Default |
|---|---|---|---|
--chart | string | chart: oci:// reference, directory, .tgz, or a chart name with --repo | oci://<release-registry>/charts/maqpna |
--create-namespace | switch | create the namespace when missing | true |
--debug | switch | print Helm's debug log to stderr | none |
--dry-run | switch | render on the API server and print the plan; change nothing | none |
-f, --values | string | values file (repeatable) | none |
--kube-context | string | kubeconfig context (default: the maqpna context's) | none |
-n, --namespace | string | namespace of the MAQPNA control plane (the Helm release) | maqpna-system |
--password | string | registry/repository password (env MAQPNA_CHART_PASSWORD) | none |
--plain-http | switch | pull the chart over plain HTTP (in-cluster test registries) | none |
--profile | string | values profile shipped with the chart: dev|prod|sovereign-eu (lowest priority) | none |
--release | string | Helm release name | maqpna |
--repo | string | chart repository URL (with --chart NAME) | none |
--set | string | set a value, KEY=VAL (repeatable) | none |
--set-file | string | set a value from a file, KEY=PATH (repeatable) | none |
--set-json | string | set a JSON value, KEY=JSON (repeatable) | none |
--set-string | string | set a string value, KEY=VAL (repeatable) | none |
--skip-crds | switch | do not apply the chart's CRDs (they must be installed already) | none |
--timeout | duration | timeout of Kubernetes operations (CRDs Established, --wait) | 10m0s |
--username | string | registry/repository username (env MAQPNA_CHART_USERNAME) | none |
--version | string | chart version (default: this CLI's version) | none |
--wait | switch | wait until every workload is ready | none |
The global flags (--context, -o, --no-color, ...) work with every command.
Examples#
# Try MAQPNA on a dev cluster (kind, k3s, minikube)
maqpna preflight --profile dev
maqpna install --profile dev --wait
# Production, with your own values
maqpna install --profile prod -f values.yaml --wait --timeout 15mWhat happens when you run it#
- Runs the lifecycle plugin
maqpna-install(next tomaqpnaor onPATH), which drives the Helm v3 SDK against the cluster of your kubeconfig (--kubeconfig,--kube-context). --dry-run: render on the API server and print the plan; change nothing.--wait: wait until every workload is ready.- Prints a table by default;
-o jsonor-o yamlprint the data, and--jq EXPRfilters 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) |
Related commands#
Terminal demo#
This command needs a Kubernetes cluster with MAQPNA installed, so the recording shows its help. Try it against a cluster from Install.