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

# Create a stack from a stack profile

> Instantiates a stack profile version on the cluster with the parameter values you supply, creating a stack draft and deploying it when `deploy` is set. Requires `stacks.write`; missing or invalid parameters, unresolvable variables and draft errors answer `400`, and a deprecated version answers `409`.



## OpenAPI

````yaml https://platform.ankra.app/openapi.json post /api/v1/org/clusters/imported/{cluster_id}/stacks/from-profile
openapi: 3.1.0
info:
  title: FastAPI
  version: 0.1.0
servers:
  - url: https://platform.ankra.app
security: []
tags:
  - name: Organisation IAM
    description: >-
      Custom organisation roles and scoped role assignments for member and
      service-account identities.
  - 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: Ankra Cloud Clusters
    description: >-
      Provision and manage self-managed kubeadm / k3s clusters on Ankra Cloud
      servers: a private network, a NAT router and a bastion per cluster.
  - 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: Pipelines
    description: Pipeline definitions and the approval of the authority they declare.
  - name: Backups
    description: >-
      Backup vaults, restore points, protection posture and captures for stacks
      and application deployments; a completed capture is not a verified
      restore.
  - name: Stack Profiles
    description: Reusable stack definitions, their versions and sharing.
  - name: Services
    description: >-
      Versioned service packages and explicit sharing. Runtime admission is
      separate from publication.
  - 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 Management
    description: >-
      Customer agent lifecycle, authenticated identity and organisation
      automation controls.
  - 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 Remediation
    description: >-
      The organisation's auto-remediation policy: what the AI lanes may fix by
      themselves, and who approves the rest.
  - 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: Decisions
    description: >-
      The decision ledger behind the Security and Cost queues: proposals a
      surface computed, the approve and set-aside decisions people took on them,
      and the receipts of running them.
  - 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: Ankra Cloud Credentials
    description: >-
      Ankra Cloud API tokens, shared by the self-managed and managed Ankra Cloud
      lanes.
  - 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: Object Storage Buckets
    description: >-
      Buckets Ankra creates and manages on an organisation's own provider
      credentials.
  - 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/org/clusters/imported/{cluster_id}/stacks/from-profile:
    post:
      tags:
        - Imported Clusters
      summary: Create a stack from a stack profile
      description: >-
        Instantiates a stack profile version on the cluster with the parameter
        values you supply, creating a stack draft and deploying it when `deploy`
        is set. Requires `stacks.write`; missing or invalid parameters,
        unresolvable variables and draft errors answer `400`, and a deprecated
        version answers `409`.
      operationId: >-
        instantiate_stack_profile_endpoint_api_v1_org_clusters_imported__cluster_id__stacks_from_profile_post
      parameters:
        - in: path
          name: cluster_id
          required: true
          schema:
            format: uuid4
            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
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/InstantiateStackProfileRequest'
        required: true
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/InstantiateStackProfileResult'
          description: Successful Response
        '401':
          description: Unauthorized
        '403':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ContractDetailError'
          description: Permission or CSRF check failed
        '404':
          description: Not found
        '422':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
          description: Validation Error
components:
  schemas:
    InstantiateStackProfileRequest:
      properties:
        deploy:
          default: false
          title: Deploy
          type: boolean
        new_stack_name:
          anyOf:
            - type: string
            - type: 'null'
          title: New Stack Name
        parameters:
          default: []
          items:
            $ref: '#/components/schemas/ParameterBinding'
          title: Parameters
          type: array
        profile_id:
          format: uuid4
          title: Profile Id
          type: string
        version:
          anyOf:
            - type: integer
            - type: 'null'
          title: Version
        upgrade_existing:
          type: boolean
          title: Upgrade Existing
          description: >-
            Replace the contents of the stack already deployed from this profile
            under new_stack_name (or the profile's stack name) with this
            version, in place, instead of creating a new stack draft. The
            stack-name and resource renames are skipped, the update is applied
            immediately (deploy is implied), and the profile's deployment
            tracking moves to the new version. Answers 404 when no stack runs
            under that name and 409 when the stack was not deployed from this
            profile.
          default: false
        allow_chart_downgrade:
          default: false
          deprecated: true
          description: >-
            Retired. It used to admit every chart downgrade in the upgrade; it
            is still accepted as a boolean (and still only together with
            upgrade_existing), but it admits nothing. Send
            confirmed_chart_downgrades instead.
          title: Allow Chart Downgrade
          type: boolean
        confirmed_chart_downgrades:
          description: >-
            The chart downgrades the person confirmed for an in-place upgrade,
            after the same request was refused with CHART_VERSION_DOWNGRADE
            because this profile version pins add-ons to older chart versions
            than the live stack declares. Each entry admits exactly the move it
            names; any other downgrade is refused again, naming every move.
            Accepted only together with upgrade_existing (422 otherwise).
          items:
            $ref: '#/components/schemas/ConfirmedChartDowngrade'
          maxItems: 200
          title: Confirmed Chart Downgrades
          type: array
      required:
        - profile_id
      title: InstantiateStackProfileRequest
      type: object
    InstantiateStackProfileResult:
      properties:
        addons_count:
          title: Addons Count
          type: integer
        deployed:
          default: false
          title: Deployed
          type: boolean
        draft_id:
          format: uuid4
          title: Draft Id
          type: string
        job_count:
          type: integer
          title: Job Count
          default: 0
        manifests_count:
          title: Manifests Count
          type: integer
        operation_id:
          anyOf:
            - format: uuid4
              type: string
            - type: 'null'
          title: Operation Id
        profile_version:
          title: Profile Version
          type: integer
        stack_name:
          title: Stack Name
          type: string
        warnings:
          default: []
          items:
            type: string
          title: Warnings
          type: array
      required:
        - draft_id
        - stack_name
        - profile_version
        - addons_count
        - manifests_count
      title: InstantiateStackProfileResult
      type: object
    ContractDetailError:
      example:
        detail: Cluster not found
      properties:
        detail:
          oneOf:
            - type: string
            - additionalProperties: true
              properties: {}
              type: object
      required:
        - detail
      type: object
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          title: Detail
          type: array
      title: HTTPValidationError
      type: object
    ParameterBinding:
      properties:
        name:
          title: Name
          type: string
        value:
          title: Value
          type: string
      required:
        - name
        - value
      title: ParameterBinding
      type: object
    ConfirmedChartDowngrade:
      description: >-
        One chart downgrade a person confirmed, exactly as a
        CHART_VERSION_DOWNGRADE refusal named it (a row of
        detail.details.downgrades may be sent back verbatim; unknown members are
        ignored). It admits that one move and nothing else: the same member,
        from the same declared version, to the same proposed version. stack and
        chart_name are optional and must match the refusal when sent.
      properties:
        member_name:
          maxLength: 253
          minLength: 1
          title: Member Name
          type: string
        declared_version:
          description: >-
            The chart version the member is declared at, as the refusal named
            it.
          maxLength: 253
          minLength: 1
          title: Declared Version
          type: string
        proposed_version:
          description: >-
            The older chart version the write moves the member to, as the
            refusal named it.
          maxLength: 253
          minLength: 1
          title: Proposed Version
          type: string
        member_kind:
          enum:
            - addon
          title: Member Kind
          type: string
        chart_name:
          maxLength: 253
          title: Chart Name
          type: string
        stack:
          maxLength: 253
          title: Stack
          type: string
      required:
        - member_name
        - declared_version
        - proposed_version
      title: ConfirmedChartDowngrade
      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

````