import requests
url = "https://platform.ankra.app/api/v1/org/clusters/imported/{cluster_id}/power-schedules/node-local-storage"
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/org/clusters/imported/{cluster_id}/power-schedules/node-local-storage', 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/org/clusters/imported/{cluster_id}/power-schedules/node-local-storage \
--header 'Authorization: Bearer <token>'{
"state": "present",
"pvc_count": 123,
"pvc_names": [
"<string>"
],
"warning": "<string>",
"consent_required": true
}{
"detail": "Cluster not found"
}{
"detail": "Cluster not found"
}{
"detail": [
{
"loc": [
"<string>"
],
"msg": "<string>",
"type": "<string>"
}
]
}{
"detail": "Cluster not found"
}The cluster's node-local storage for a scale_to_zero stop
The bearer twin of the portal’s node-local storage read (ankra cluster power-schedules create|update reads it before a scale_to_zero stop). Answers which persistent volume claims keep their data on a worker’s own disk, which a scale_to_zero stop deletes at every stop. A failed or empty inventory read is unknown, never none.
import requests
url = "https://platform.ankra.app/api/v1/org/clusters/imported/{cluster_id}/power-schedules/node-local-storage"
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/org/clusters/imported/{cluster_id}/power-schedules/node-local-storage', 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/org/clusters/imported/{cluster_id}/power-schedules/node-local-storage \
--header 'Authorization: Bearer <token>'{
"state": "present",
"pvc_count": 123,
"pvc_names": [
"<string>"
],
"warning": "<string>",
"consent_required": true
}{
"detail": "Cluster not found"
}{
"detail": "Cluster not found"
}{
"detail": [
{
"loc": [
"<string>"
],
"msg": "<string>",
"type": "<string>"
}
]
}{
"detail": "Cluster not found"
}Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Response
The cluster's node-local storage finding.
What a scale_to_zero stop loses on this cluster: the persistent volume claims the synced inventory shows keeping their data on a worker's own disk.
present (at least one claim keeps data on a worker disk), none, or unknown (the inventory holds no nodes for the cluster, or could not be read). Unknown is never taken as none.
present, none, unknown How many claims keep data on a worker disk; null when state is unknown.
Up to 25 of those claims as namespace/name, sorted; null when state is unknown.
The sentence to show before such a stop is written; empty on none.
True exactly when the power schedule writes refuse an enabled scale_to_zero stop without accept_node_local_data_loss (state present).