> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ankra.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Get OVH 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.



## OpenAPI

````yaml https://platform.ankra.app/openapi.json get /api/v1/clusters/ovh/{cluster_id}/k3s-disabled-components
openapi: 3.1.0
info:
  title: FastAPI
  version: 0.1.0
servers:
  - url: https://platform.ankra.app
security: []
tags:
  - name: Clusters
    description: Create, inspect and manage clusters, and the stacks deployed on them.
  - name: Managed Clusters
    description: Provider-managed control planes, driven through one common surface.
  - name: Imported Clusters
    description: Clusters that already existed and were connected to Ankra.
  - name: Cluster Access
    description: Kubeconfigs, service-account tokens and per-cluster access grants.
  - name: Kubernetes
    description: Read and act on the Kubernetes objects inside a cluster.
  - name: AWS Clusters
    description: >-
      Provision and manage self-managed k3s / kubeadm clusters on AWS EC2 in
      your own VPC.
  - name: DigitalOcean Clusters
    description: Provision and manage DigitalOcean Kubernetes clusters.
  - name: Hetzner Clusters
    description: Provision and manage Hetzner Kubernetes clusters.
  - name: OVH Clusters
    description: Provision and manage OVH Kubernetes clusters.
  - name: Scaleway Clusters
    description: Provision and manage Scaleway Kapsule clusters.
  - name: UpCloud Clusters
    description: Provision and manage UpCloud Kubernetes clusters.
  - name: Applications
    description: Deploy, configure and observe applications across the fleet.
  - name: Stack Profiles
    description: Reusable stack definitions, their versions and sharing.
  - name: Charts
    description: Browse the chart catalogue behind stacks and addons.
  - name: Helm
    description: Helm registries, credentials and the charts they expose.
  - name: Executions
    description: Long-running platform executions and their jobs.
  - name: Operations
    description: Cancel in-flight cluster operations and their jobs.
  - name: Chat
    description: Conversational sessions, plans and confirmable actions.
  - name: AI Agent Runs
    description: Autonomous agent runs and their outcomes.
  - name: AI Tickets
    description: The AI ticket board, its sync connections and settings.
  - name: AI Playbooks
    description: Reusable playbooks the AI lanes execute.
  - name: AI Conditions
    description: Conditions that gate AI autonomy.
  - name: AI Engineering Handoffs
    description: Work the AI lanes escalate to a human engineer.
  - name: AI Environment
    description: The environment and base stacks AI demos deploy into.
  - name: Security
    description: Findings, advisories, SBOMs, compliance and posture.
  - name: Cost
    description: Cluster and fleet cost, rate cards and cost settings.
  - name: Billing
    description: Subscription and spend caps.
  - name: Organisation
    description: Members, invitations, audit logs and organisation settings.
  - name: Account Tokens
    description: Personal access tokens for the API and CLI.
  - name: Credentials
    description: The shared credential store.
  - name: AWS Credentials
    description: >-
      AWS credentials: access keys or CloudFormation-onboarded STS roles for
      cost, EKS and self-managed provisioning.
  - name: Azure Credentials
    description: Azure credentials and SSH keys.
  - name: DigitalOcean Credentials
    description: DigitalOcean credentials and SSH keys.
  - name: Hetzner Credentials
    description: Hetzner credentials and SSH keys.
  - name: OVH Credentials
    description: OVH credentials and SSH keys.
  - name: Scaleway Credentials
    description: Scaleway credentials.
  - name: UpCloud Credentials
    description: UpCloud credentials and SSH keys.
  - name: Data Source Credentials
    description: Credentials for metrics and log sources.
  - name: DNS Credentials
    description: Credentials for DNS providers.
  - name: DNS
    description: DNS zones and records, including custom organisation zones.
  - name: Cloudflare
    description: Cloudflare domains and the credentials behind them.
  - name: Variables
    description: Organisation- and cluster-scoped variables.
  - name: SOPS
    description: Encrypt and decrypt values with the organisation SOPS config.
  - name: Alerts
    description: Alert integrations and ingest credentials.
  - name: Notifications
    description: Notification routes and their delivery targets.
  - name: Support
    description: Support tickets.
  - name: AI Settings
    description: Organisation AI provider, model catalog and per-function model settings
paths:
  /api/v1/clusters/ovh/{cluster_id}/k3s-disabled-components:
    get:
      tags:
        - OVH Clusters
      summary: Get OVH K3s Disabled Components Endpoint
      description: >-
        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.
      operationId: >-
        get_ovh_k3s_disabled_components_endpoint_api_v1_clusters_ovh__cluster_id__k3s_disabled_components_get
      parameters:
        - in: path
          name: cluster_id
          required: true
          schema:
            format: uuid
            title: Cluster Id
            type: string
        - in: header
          name: authorization
          required: false
          schema:
            anyOf:
              - type: string
              - type: 'null'
            title: Authorization
        - in: header
          name: x-ankra-organisation-id
          required: false
          schema:
            anyOf:
              - type: string
              - type: 'null'
            title: X-Ankra-Organisation-Id
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/K3sDisabledComponentsResult'
          description: Successful Response
        '401':
          description: Unauthorized
        '404':
          description: Not found
        '409':
          description: Invalid state
        '422':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
          description: Validation Error
components:
  schemas:
    K3sDisabledComponentsResult:
      properties:
        k3s_disabled_components:
          items:
            type: string
          title: K3S Disabled Components
          type: array
          description: >-
            The components stored on the cluster's k8s node definitions; empty
            when nothing is stored (the provider shape's own defaults apply).
        resource_ids:
          items:
            type: string
          title: Resource Ids
          type: array
          description: >-
            The cluster's live k8s node resources (control planes and workers)
            the list is stored on.
        control_plane_count:
          title: Control Plane Count
          type: integer
          description: >-
            How many of those resources are control planes, the nodes the
            disable list is rendered on.
        applies:
          title: Applies
          type: string
          description: >-
            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.
      required:
        - k3s_disabled_components
        - resource_ids
        - control_plane_count
        - applies
      title: K3sDisabledComponentsResult
      type: object
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          title: Detail
          type: array
      title: HTTPValidationError
      type: object
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          title: Location
          type: array
        msg:
          title: Message
          type: string
        type:
          title: Error Type
          type: string
      required:
        - loc
        - msg
        - type
      title: ValidationError
      type: object

````