Skip to main content
Draftt brings Kubernetes resources, policy results, and upgrade readiness into one view. Use it to understand what is running across connected clusters, identify resources that need attention, and plan the changes required for a cluster upgrade.

​
Resource catalog

The Kubernetes Resource Catalog provides a searchable view of supported native Kubernetes resources and Custom Resource Definitions (CRDs) discovered across connected clusters. Explore resources by cluster, namespace, kind, API version, label, ownership classification, and management context. Each resource includes relevant details such as its container images, served CRD API versions, and whether it is managed through Helm, Argo CD, or Flux. This helps you understand how each resource is configured, who owns it, and how changes should be delivered.

​
Inventory

Kubernetes Inventory combines cataloged resources with their policy evaluation results. It shows the compliance status of each resource for the selected policies, along with the context needed to investigate and address the result. Use filters and saved views to focus on specific clusters, namespaces, resource kinds, labels, or policy statuses.

​
Upgrade plan

When a target Kubernetes version is available for a cluster, Draftt creates a cluster-specific upgrade plan. The plan brings together the changes required across:
  • The control plane
  • Nodes
  • Kubernetes API resources
  • CRDs
  • Workloads
  • Container images
Each item retains its relevant ownership and management context, including whether it is managed through Helm, Argo CD, or Flux. Use the plan to understand upgrade requirements, assign ownership, sequence remediation work, and track progress toward the target version. Use the Draftt MCP to make the upgrade plan available to an LLM or coding agent. The agent can then generate cluster-specific commands and remediation steps based on Draftt’s guidance. To connect a cluster and install the collector, see Kubernetes. Kubernetes policies evaluate resource configuration, organizational standards, and compatibility with target Kubernetes versions. See Governance policies.

​
Common use cases

  • Understand what is running. Build a current inventory of resources across clusters and namespaces. Explore their configuration, ownership, API versions, labels, container images, relationships, and management through Helm, Argo CD, or Flux.
  • Investigate policy results. Identify resources that require attention and prioritize them by policy status. Use their configuration, ownership, cluster, and management context to understand each result and determine the appropriate remediation path.
  • Prepare for a Kubernetes upgrade. Identify the changes required across the control plane, nodes, APIs, CRDs, workloads, and container images before moving to a target Kubernetes version.
  • Coordinate upgrade execution. Use the upgrade plan to assign ownership, sequence remediation work, and maintain a shared view of upgrade progress. Connect the plan to your coding agent through the Draftt MCP to generate implementation guidance grounded in the cluster’s actual context.