Run Clusterlint Checks on a Kubernetes Cluster
Clusterlint helps operators conform to Kubernetes best practices around resources, security and reliability to avoid common problems while operating or upgrading the clusters.
To request a clusterlint run on your cluster, send a POST request to /v2/kubernetes/clusters/$K8S_CLUSTER_ID/clusterlint. This will run all checks present in the doks group by default, if a request body is not specified. Optionally specify the below attributes.
For information about the available checks, please refer to the clusterlint check documentation.
Path parameters
A unique ID that can be used to reference a Kubernetes cluster.
Request body
Example request
{
"include_groups": [
"basic",
"doks",
"security"
],
"include_checks": [
"bare-pods",
"resource-requirements"
],
"exclude_groups": [
"workload-health"
],
"exclude_checks": [
"default-namespace"
]
}Response
The response is a JSON object with a key called run_id that you can later use to fetch the run results.
Example response
{
"run_id": "50c2f44c-011d-493e-aee5-361a4a0d1844"
}Changes
Changed in 4 of the 8 revisions of this API.14
- ○
api tag
DigitalOcean-public.v2-new_Kubernetesaddedapi-tag-added
- ○
api tag
Kubernetesremovedapi-tag-removed
This revision also has 3 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○
- ○
endpoint added
endpoint-added
This revision also has 70 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○
- ▲
api path removed without deprecation
api-path-removed-without-deprecation
This revision also has 436 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲
- ○
endpoint added
endpoint-added
This revision also has 70 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○