Skip to main content
Connect your Kubernetes clusters to Draftt to detect version compatibility issues, track configuration drift, and get actionable upgrade plans. Draftt uses a lightweight Helm-based collector deployed into your cluster. Learn how Draftt catalogs and governs cluster resources in Kubernetes governance.

​
Prerequisites

  • A Kubernetes cluster with kubectl configured and pointing to the correct context
  • Helm installed on your machine
  • A Draftt account with tenant admin permissions (to create an access key)

​
Setup

1

Select a cluster

In Draftt, go to Integrations > K8s Explorer > Add. Select the cluster you want to connect.
2

Add the Draftt Helm repository

Add and update the Draftt Helm chart repository:
3

Create a Draftt API access key

Navigate to Settings > Access Keys in Draftt. Create a new access key with tenant admin permissions. Save the key. You will need it in the next step.
4

Create a Kubernetes Secret

The commands below assume that you deploy Draftt Explorer in an existing monitoring namespace. You can use a different namespace, but you must update the namespace in each command accordingly.
Create a Secret to store your Draftt API key:
5

Install the Helm chart

Install the Draftt Explorer chart:
Replace <YOUR_K8S_CLUSTER_IDENTIFIER> with a name that identifies this cluster in Draftt (for example, arn:aws:eks:us-east-1:12345678910:cluster/production-us-east-1).
6

Validate the integration

Run the collector job manually to verify everything is working:
Check the job logs to confirm that data was sent to Draftt successfully. Once validated, the collector runs automatically on its configured schedule.

​
Upgrade from Draftt collector agent version 0.0.1

Use these instructions to upgrade an existing Draftt collector installation from agent version 0.0.1.
1

Update the Draftt Helm repository

2

Review the current release values

Review the values currently set for the release. Identify any values supported by agent v2 that should remain configured after the upgrade.
The next step uses --reset-values, so Helm will not retain these values automatically.
3

Upgrade the collector

--reset-values removes the stored legacy values and applies the agent v2 chart defaults. To reapply values identified in the previous step, use:
  • --set or --set-string for individual values
  • --values <VALUES_FILE> or -f <VALUES_FILE> for a values file
4

Verify the upgrade

​
What Draftt collects

Draftt Explorer is a read-only collector. It discovers resources exposed through the Kubernetes API and sends their metadata and configuration to Draftt for analysis. It does not modify cluster resources. * Configuration refers to the Kubernetes resource spec. Collected metadata includes:
  • Resource identity
  • Namespace
  • API version
  • Labels
  • Annotations
  • Owner references
  • Management signals
Draftt does not collect sensitive information from the cluster. All collected configuration is sanitized before it is sent to Draftt.

​
Supported environments

The Helm-based collector works with any Kubernetes distribution: managed services (EKS, AKS, GKE), self-managed clusters, and on-premises deployments. Connect multiple clusters by repeating the setup for each one.

​
Verify your connection

After the test job completes, return to Integrations > K8s Explorer in Draftt. The connected cluster shows a status:
  • Healthy — The collector is running and Draftt is receiving data.
  • Unhealthy — Check that the API key Secret exists in the correct namespace, the Helm chart is installed, and the CronJob is scheduled.

​
Troubleshooting

Job fails with authentication error: Verify the draftt-api-token secret exists in the correct namespace and contains a valid API key with tenant admin permissions. No data appearing in Draftt: Confirm the clusterIdentifier value matches what you expect in the Draftt dashboard. Check the job logs with kubectl logs job/draftt-test-run -n monitoring. Helm install fails: Ensure the Draftt Helm repo was added and updated (helm repo update). Verify the target namespace exists (kubectl create namespace monitoring if needed).