Skip to main content
Most cluster problems start small - a pod restarting, a node filling up - and are noticed only when they page someone. With AI Insights on, Ankra AI checks your clusters’ health by itself and gives each problem it finds a likely cause, the steps to fix it and questions to ask Ankra AI. When an alert does fire, a notification carries an AI analysis, so the first person to look starts with an explanation instead of a blank log view. The health check is off until an owner or admin turns it on for the organisation. The alert analysis below works without it.

Before you start

  • Turning the health check on or off for the organisation needs a role that manages the organisation, such as owner or admin. Anyone else sees the switch but cannot change it.
  • Each cluster has its own switch, which is on by default. A cluster is checked only when both switches are on.

Turn on the health check

1

Open Autonomy and approvals

Go to Ankra AI → Autonomy and approvals (/next/organisation/ai-autonomy) and scroll to Finding problems on its own.
2

Switch it on

Turn on Check cluster health on its own. It is off by default.The switch now reads on, and the settings below it become active.
3

Tune the check (optional)

  • Restarts before a pod counts as unstable - leave it empty to use the platform’s default.
  • Hours that restarts are counted over - only restarts within this many hours count. Leave it empty for the default.
  • Leave out system namespaces - skips kube-system and the other system namespaces when checking workloads.
Press Save changes.

Leave one cluster out

  1. Go to Infrastructure → Clusters → <your cluster> → Settings → Ankra AI (/next/clusters/<cluster-id>/settings/ai).
  2. In the Ankra AI insights card, press Turn Ankra AI insights off, then confirm with Turn Ankra AI insights off in the dialog.
Ankra AI stops watching that cluster for problems. Insights it already raised stay, and you can still ask it about the cluster. The card reads Off for this cluster. Turn it back on the same way with Turn Ankra AI insights on. If the organisation’s switch is off, the card says so whatever the cluster’s switch is: Ankra AI insights are also off for the whole organisation, with a link to Ankra AI insights for the organisation.

Where the problems it finds go

The health check does not have a page of its own in the portal. What it finds reaches people through the places they already work: With the health check off, nothing is filed or sent from it, and no ticket or fix is started from a health check. You can still ask Ankra AI about a cluster at any time with ⌘J.

Alert-triggered analysis

When an alert fires, Ankra AI writes an analysis from what Ankra has recorded about the alert: the rule that fired, the resource it names and, where there is one, the failed job or operation behind it. The analysis does not read live state from the cluster, so for current pod status, events or logs, ask Ankra AI about the resource. The analysis is attached to the alert’s notification. To read it, open the notification from the bell (/next/notifications/<id>). Its AI analysis section holds:
  • A summary of what happened.
  • Likely cause - the underlying problem behind the symptom.
  • Recommended actions - what to do next.
  • Read full analysis - the complete write-up.
While the analysis is being written, the section reads Analysis is being prepared. This page updates automatically. If none was saved, it reads No saved analysis is available for this notification. A firing can also start auto-remediation under the remediation policy, and the alert itself is listed under Ankra AI → Watching.

Which model reads it

Neither the health check nor the analysis on an alert follows the provider your organisation chose under Ankra AI → Models and provider.
  • The analysis on an alert always runs on Ankra’s own access to Groq. It is sent the alert and rule names, the names of the resource and the cluster, the failed job’s error messages and the start of its command output, and the Kubernetes events recorded with a failed health check. It is not sent pod logs.
  • The health check runs on Ankra’s own access too: Groq first, and a Claude model if that fails. It counts against your plan’s monthly AI allowance. Once the allowance is used up, it runs on your organisation’s own key if you added one.
The sub-processor list at ankra.ai/trust names OpenRouter (LLM routing), Groq (LLM inference) and Voyage AI (embeddings) for Ankra’s AI features. Models and cost covers what your own provider key serves.

Next

Decide what Ankra AI may do on its own when an alert fires: AI Autonomy.