Skip to content

lookout cloud quota

Per-project cloud quota usage vs limit, ranked nearest-to-exhaustion: findings from —quota-warn (default 80%), critical at 95% — quota is incompressible (scale-ups fail at the limit) and increases need lead time. Trend/ETA lives in the quota source.

MCP tool: k8s_cloud_quota

Terminal window
lookout cloud quota [flags]
FlagTypeDefaultMeaning
--quota-warnint80report a quota only at or above this percent of its limit (critical is fixed at 95%)
--allbool—exploratory dump: emit every ratable quota regardless of —quota-warn (info severity below it), sorted by pct descending
FlagTypeDefaultMeaning
--namespacestring—limit the scan to one namespace
-Abool—scan all namespaces
--workloadstring—target one workload as <Kind>/<namespace>/<name>, e.g. Deployment/prod/api
--sinceduration—how far back to look (0 = command default)
--formatstringlogfmtoutput format: logfmt|json (one record per line either way)
--timeoutduration10sabort the invocation after this long (exit 1)
--kubeconfigstring—path to a kubeconfig file, instead of $KUBECONFIG / ~/.kube/config
--contextstring—kubeconfig context to read, instead of its current-context. Selects a cluster for THIS invocation only — nothing is written back — so concurrent invocations can target different clusters. Reported as context=<name> in the summary line
--exemptionsstring—path to a git-reviewed exemption file (YAML); covered findings are ANNOTATED with their reason and expiry and counted as exempt=<n> in the summary, never dropped

Every kind= this command can emit, and the severities it carries them at. Nothing else appears in its output; a kind absent from a run means the check looked and found nothing. See the finding-kind glossary for the whole vocabulary.

KindSeverityClaim
quota.pressurecritical, warning, infoa cloud quota is at or above —quota-warn percent of its limit; critical from 95%, info for an —all row below the line
cloud.unavailableinfothe cloud capability this check needs is unavailable, so nothing was examined — an explicit degradation record, never silence

Beyond the shared envelope fields (kind, severity, namespace, kind_of_object, name, reason, message, fingerprint, exempt_reason, exempt_expires):

FieldMeaning
scopethe quota’s scope: a region name, or “global”
usagecurrent usage in the quota’s own unit
limitthe quota limit
unitthe quota’s unit, when the provider names one
pctusage as a percent of the limit, one decimal
capabilitycloud.unavailable: the provider capability this command needed (quota)
providercloud.unavailable: the provider that was asked
unavailablesummary-line note: why the cloud read could not be served

Output: one finding per line (logfmt; —format=json for one JSON object per line), keys in fixed order; healthy resources emit nothing. The final line is always the summary: scanned= findings= elapsed= — findings=0 with a summary present means “scanned and healthy”; a stream without a summary line is void. Exit 0 data, 1 runtime error (diagnostics on stderr only), 2 usage.

Terminal window
lookout cloud quota
lookout cloud quota --quota-warn=60
lookout cloud quota --all --format=json