AI Center
Purpose
AI-assisted SRE, migration, and security advisors grounded in cluster evidence (Forge / built-in LLM when configured).
When to use it
- Ask for remediation suggestions with citations
- Draft manifests or runbooks with guardrails
- Pair with Incidents / Auto-Remediation for day-2 loops
How to get there
- Route:
/ai-center - Related:
/forge,/nlp-command, Settings → AI providers
Operate from the console (UX)
- Open
/ai-centerfrom the sidebar, workspace switcher, or command palette (⌘K / Ctrl+K). - Read the editorial hero and Get the highlights, then pick an advisor (SRE, migration, security, cost, capacity, network).
- Use the center’s primary CTA (create, scan, open workbench, ask Zeus when reasoning is required).
- Deterministic navigation and filters call the router directly — do not round-trip those through Ask Zeus.
- Pin frequent pages to Favorites (
/favorites). - Empty / fail: No data → check auth, namespace filter, and that required operators (KubeVirt/CDI/monitoring) are installed; purpose was: AI-assisted SRE, migration, and security advisors grounded in cluster evidence (Forge / built-in LLM.
- Success: Live inventory or job progress matches the deck line; you can navigate to a related center without re-auth.
Use https://<host>:30050/ (NodePort) or your ingress URL — never publish lab IPs. HTTPS is required for in-browser VNC. Browse lists are safe; power actions live on workbenches.
Related pages
- Incidents
- Auto-Remediation —
/auto-remediation - Settings