Skip to main content
GET
/
api
/
v1
/
org
/
clusters
/
imported
/
{cluster_id}
/
addons
/
{addon_name}
/
configuration
Get Addon Values Endpoint
import requests

url = "https://platform.ankra.app/api/v1/org/clusters/imported/{cluster_id}/addons/{addon_name}/configuration"

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}/addons/{addon_name}/configuration', 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}/addons/{addon_name}/configuration \
  --header 'Authorization: Bearer <token>'
{
  "result": {
    "cluster_addon_configuration": {
      "encrypted_paths": [],
      "values": "<string>"
    }
  }
}
{
  "detail": [
    {
      "loc": [
        "<string>"
      ],
      "msg": "<string>",
      "type": "<string>"
    }
  ]
}

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

​
authorization
string | null
​
x-ankra-organisation-id
string | null

Path Parameters

​
cluster_id
string<uuid4>
required
​
addon_name
string
required

Response

Successful Response

Response shape mirrors the v2 web endpoint so existing clients (the Ankra CLI) can parse result.cluster_addon_configuration.values directly. Unlike v2 this endpoint never touches the cluster agent or Argo CD: it reads the DB-stored plaintext base64 values only.

​
result
ClusterAddonValuesResult · object | null