import requests
url = "https://platform.ankra.app/api/v1/clusters/upcloud/{cluster_id}/k3s-disabled-components"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://platform.ankra.app/api/v1/clusters/upcloud/{cluster_id}/k3s-disabled-components', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));curl --request GET \
--url https://platform.ankra.app/api/v1/clusters/upcloud/{cluster_id}/k3s-disabled-components \
--header 'Authorization: Bearer <token>'{
"k3s_disabled_components": [
"<string>"
],
"resource_ids": [
"<string>"
],
"control_plane_count": 123,
"applies": "<string>"
}{
"detail": [
{
"loc": [
"<string>"
],
"msg": "<string>",
"type": "<string>"
}
]
}Get UpCloud K3s Disabled Components Endpoint
Read the k3s packaged components the platform keeps disabled on this running cluster (k3s —disable), on top of the provider shape’s own defaults. The list is stored on every k8s node definition of the cluster. The maintenance read lane compares each control plane’s k3s server config against it within about five minutes and flags the ones missing an entry; the reconcile lane then patches the config and restarts k3s on one control plane at a time, in the cluster’s k8s update chain. Control planes already carrying every entry are not touched. Invalid states (a kubeadm or Scaleway cluster, no k8s node resources, a cluster of another provider) answer 409 with a detail message.
import requests
url = "https://platform.ankra.app/api/v1/clusters/upcloud/{cluster_id}/k3s-disabled-components"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://platform.ankra.app/api/v1/clusters/upcloud/{cluster_id}/k3s-disabled-components', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));curl --request GET \
--url https://platform.ankra.app/api/v1/clusters/upcloud/{cluster_id}/k3s-disabled-components \
--header 'Authorization: Bearer <token>'{
"k3s_disabled_components": [
"<string>"
],
"resource_ids": [
"<string>"
],
"control_plane_count": 123,
"applies": "<string>"
}{
"detail": [
{
"loc": [
"<string>"
],
"msg": "<string>",
"type": "<string>"
}
]
}Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Response
Successful Response
The components stored on the cluster's k8s node definitions; empty when nothing is stored (the provider shape's own defaults apply).
The cluster's live k8s node resources (control planes and workers) the list is stored on.
How many of those resources are control planes, the nodes the disable list is rendered on.
How the stored list reaches the nodes: the read lane flags control planes missing an entry within about five minutes and the reconcile lane converges them one at a time.