Clusters, components and routed Services.
| Command | Use it to | What it reports |
|---|---|---|
aide cluster list | See every registered cluster | Name, domain, status and runtime. Needs no project file |
aide cluster status | Check the project's cluster | Component, DNS and trust indicators |
aide cluster use <NAME> | Pick the default cluster | Sets the default cluster and the kubectl context; the name must be a running cluster |
aide route list | See routed Services | Services that carry routing annotations, with mode and endpoint. -n selects the namespace (default apps) |
aide route status | Check overrides | The same list, plus a reachability check of each override |
Status indicators describe the cluster, not your application. A green status does not show that a hostname resolves, that the certificate is trusted or that a response body is right; check those with getent hosts and curl.
One report for credentials, tools, updates and connectivity.
aide doctor checks credentials, each managed tool, the privileged helper, update status and whether MAIT services answer. aide setup --check reports only the managed dependencies and exits 1 when one is missing.
doctor exits 0 even when it reports errors, so read the findings and the final counts rather than the status. aide setup without --check installs what is missing and can be repeated. The troubleshooting page separates setup, DNS, TLS and routing failures.
Check for a newer release, then confirm what runs.
aide update checks the MAIT update service with your credentials and stages a verified download. It asks for confirmation, so it needs a terminal. The next aide command you run (except aide legal), including aide version, switches to the downloaded release before it runs, so aide version then reports the newer release; if aide cannot switch, it prints a warning and runs your command with the installed release (see the update entry in Troubleshooting). You can also install a newer release through aidc install mait:aide@latest.
aide legal prints the copyright and the third-party components built into the binary; --full, --json and --markdown change the form.
Suspend a cluster, delete it, or remove aide.
| Command | What it does | Keep in mind |
|---|---|---|
aide cluster stop | Suspends the cluster and keeps its state | aide cluster start resumes it and reapplies DNS and trust |
aide cluster delete | Deletes the cluster and attempts DNS, trust and network cleanup | --purge also removes the named volumes. Preserve data first |
aide route reset <SERVICE> | Clears overrides and routing annotations | Use it when a partial switch leaves a Service pointing at the wrong place |
Delete each cluster from its project directory, or pass --project-file, and then check that its name no longer resolves and its aide-<project>.crt trust entry (the file /usr/local/share/ca-certificates/aide-<project>.crt) is gone. To remove AIDE itself, remove the administrator helper that aide setup added (the steps are in the getting-started page), then remove the binary the way it was installed, for example aidc uninstall mait:aide@<version> with the exact version from aidc list mait. The getting started page lists every step.