From cluster signal to a safe next action.

Your first automatic review

After the first accepted agent report, KrevoPilot maps applications, pod readiness, Kubernetes warnings, resource usage and supported topology relationships. It does not change the cluster from Overview.

Overview

Overview is the decision page for the selected cluster. Its health, application, optimization, activity and capacity numbers come from the same cluster snapshot or stored analysis.

Cards and rows are interactive. Select a segment or issue to open focused details; application links should resolve to the exact application or pod rather than the general list.

Clusters

Clusters is the connection control center. It distinguishes healthy agents, offline saved connections and incomplete setup. Each row shows the last report, detected environment, agent/image/chart version and available update.

• Open cluster selects it for the dashboard.
• Fix connection preserves the saved record and history.
• Upgrade generates a release-specific command.
• Technical details exposes safe identifiers and diagnostic status.

Applications and topology

Applications groups Kubernetes controllers into recognizable application names using real agent data. Open a card to see its namespace, controller, pods, services, EndpointSlices, ingress, configuration references and storage relationships when collected.

Real resource names appear when identifier collection is enabled. Privacy aliases are used when a workspace intentionally hides identifiers; they should not coexist as duplicate rows for the same application.

Krevo AI investigations

Select an unhealthy pod and run an investigation. The result opens on Fix and keeps Verdict, Evidence, Logs, Events, YAML, Timeline, Verification and Hypotheses one click away.

Commands are recommendations, not automatic execution. Validate the cluster context, object name and generated change. See the published benchmark for bounded accuracy and limitations.

Optimize

Optimize analyzes resource requests against observed usage history. CPU and memory are evaluated separately, so a workload can need less CPU and more memory at the same time.

A recommendation shows current request, average, P95, peak, suggested request, samples, history, confidence and evidence. Zero meaningful use is categorized as an idle-workload review rather than a normal request of zero. When requests or limits change, a new resource-configuration epoch starts so old settings do not drive the new recommendation.

Deploy and GitOps

Start with a ready-made tool, your container image or a plain-language plan. Choose the target cluster, cluster type and delivery method. GitOps can push generated files to a connected repository for Argo CD to sync; download mode keeps delivery manual.

• Required fields have an asterisk and turn red when missing.
• Review generated manifests before deployment.
• Saved deployments are isolated to the workspace and can be deleted.
• Cluster facts such as namespaces, storage classes, ingress classes and Argo CD detection are clickable when available.

Teams & Access

Owners and Admins manage users, roles, teams and cluster assignments. Workspace membership decides the tenant; team assignment can further narrow which clusters a member can access.

Audit attribution should identify the acting user for access, deployment and investigation actions.

SSO / OIDC

1. An Owner opens Teams & Access → Single sign-on.
2. Register KrevoPilot’s exact callback URL with the identity provider.
3. Enter issuer URL, client ID, secret and one or more company domains.
4. Test the provider, enable SSO, then complete one real sign-in.
5. Choose whether permitted-domain users are pre-provisioned or automatically created.
6. After validation, optionally require SSO while retaining the documented Owner recovery path.

New SSO users receive the workspace’s default role and remain unassigned until an Owner places them in the correct team and cluster scope.