> ## 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 profile from a Helm chart > Makes one Helm chart from a registry your organisation can use into a stack profile and stores its first version, so a managed service can be published over it: one stack holding the chart, installed into the namespace named after each service. With `generated_secret`, the profile also carries a credentials release that generates that Secret's keys in the service's cluster on the first install and keeps them on every upgrade; Ankra never sees the values. Answers 201 with the profile and the version, and 422 naming the field a request cannot be built from. ## OpenAPI ````yaml https://platform.ankra.app/openapi.json post /api/v1/org/stack-profiles/from-chart openapi: 3.1.0 info: title: FastAPI version: 0.1.0 servers: - url: https://platform.ankra.app security: [] tags: - name: Onboarding description: >- Generate a first website from a prompt and deploy it to a new organisation's cluster. - name: Access Gate description: >- Private service sign-in and membership checks for trusted Ankra proxy relays. - name: Canvas Datasets description: >- Read the fixed, named datasets canvas dashboards bind their charts, tables and stats to. - name: Canvases description: >- Keep dashboards and pages in the organisation's canvas library, with revision history, undo and pins. - name: Canvas Pages description: >- Publish a chat canvas artifact at a public pages address and take it down again. - name: Cloud Delegation description: >- Platform browser consent and organisation-bound connections for Ankra Cloud. - 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, the approval of the authority they declare, and the caches pipelines keep between runs. - name: Workspaces description: >- Personal workspaces on the organisation's CI pool where a repository's heavy commands run, and the repository profiles they are built from. - name: Deploy Targets description: >- Environments, the hosts registered to receive deployments, and the releases deployed to them. - name: Deploy Provenance description: >- Whether an application's deploys verify signed provenance from the organisation's own pipeline, the keys that provenance is signed with, and a dry-run that verifies images without deploying. - 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: AI Memory description: >- What the assistant has learned about you: your cross-session memories and learned profile. - name: MCP Servers description: >- Register the MCP servers the organisation's AI agents can call, choose their tools and grant them to roles. - 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: Usage description: >- What your organisation used of Ankra - vCPU-hours, playgrounds, managed services, hosted logs and metrics, and AI - per meter and period, with how completely it was measured and whether a published rate applies. - name: Billing description: Subscription and spend caps. - name: Organisation description: Members, invitations, audit logs and organisation settings. - name: Account description: >- Your own account: the contact email Ankra mails when it differs from your sign-in address. - 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: Avura description: >- The linked Avura organization, the domains it shares with Ankra Platform, and their DNS records. - name: Variables description: Organisation- and cluster-scoped variables. - name: Secret Slots description: >- Store secrets in Vault and reference them by ${SECRET_SLOT:} sentinel instead of by value. - 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/stack-profiles/from-chart: post: tags: - Stack Profiles summary: Create a stack profile from a Helm chart description: >- Makes one Helm chart from a registry your organisation can use into a stack profile and stores its first version, so a managed service can be published over it: one stack holding the chart, installed into the namespace named after each service. With `generated_secret`, the profile also carries a credentials release that generates that Secret's keys in the service's cluster on the first install and keeps them on every upgrade; Ankra never sees the values. Answers 201 with the profile and the version, and 422 naming the field a request cannot be built from. operationId: createChartServiceProfileToken requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/ChartServiceProfileRequest' responses: '201': description: Stack profile created content: application/json: schema: $ref: '#/components/schemas/CreateStackProfileResult' '400': description: The body is not a valid chart profile request '401': description: Unauthorized '403': description: Forbidden '409': description: Profile name conflict '413': description: Request body too large '422': description: >- The request names a registry, chart, version or generated Secret a profile cannot be built from '500': description: Internal server error security: - BearerAuth: [] components: schemas: ChartServiceProfileRequest: type: object additionalProperties: false required: - name - chart_name - chart_version - registry_name description: >- One Helm chart to make into a stack profile a managed service can be published over. properties: name: type: string description: 'The profile''s name and its one stack''s: a Kubernetes name.' description: type: string chart_name: type: string chart_version: type: string registry_name: type: string description: >- A Helm registry as registered in Ankra: the organisation's own of that name, or the shared catalogue's. values_yaml: type: string description: The chart's values document, at most 256 KiB. generated_secret: $ref: '#/components/schemas/GeneratedServiceSecret' CreateStackProfileResult: properties: profile: $ref: '#/components/schemas/StackProfileSummary' version: type: object additionalProperties: true warnings: type: array items: type: string required: - profile - version - warnings title: CreateStackProfileResult type: object GeneratedServiceSecret: type: object additionalProperties: false required: - name - keys description: >- The Secret Ankra generates in each service's namespace, before the chart is installed and kept on every upgrade. properties: name: type: string description: A Kubernetes name. keys: type: array minItems: 1 maxItems: 16 items: $ref: '#/components/schemas/GeneratedServiceSecretKey' StackProfileSummary: properties: id: type: string format: uuid organisation_id: type: string format: uuid name: type: string description: anyOf: - type: string - type: 'null' logo_url: anyOf: - type: string - type: 'null' has_uploaded_logo: type: boolean uploaded_logo_updated_at: anyOf: - type: string format: date-time - type: 'null' category: type: string tags: type: array items: type: string visibility: enum: - organisation - public type: string latest_version: type: integer current_version: type: integer source_cluster_id: anyOf: - type: string format: uuid - type: 'null' created_by_user_id: anyOf: - type: string - type: 'null' created_at: type: string format: date-time updated_at: type: string format: date-time publisher_name: anyOf: - type: string - type: 'null' publisher_slug: anyOf: - type: string - type: 'null' publisher_verified: type: boolean publisher_is_ankra: type: boolean publisher_has_logo: type: boolean publisher_logo_updated_at: anyOf: - type: string format: date-time - type: 'null' shared_organisation_count: type: integer shared_with_you: type: boolean is_owner: type: boolean required: - id - organisation_id - name - description - logo_url - has_uploaded_logo - uploaded_logo_updated_at - category - tags - visibility - latest_version - current_version - source_cluster_id - created_by_user_id - created_at - updated_at - publisher_name - publisher_slug - publisher_verified - publisher_is_ankra - publisher_has_logo - publisher_logo_updated_at - shared_organisation_count - shared_with_you - is_owner title: StackProfileSummary type: object GeneratedServiceSecretKey: type: object additionalProperties: false required: - key description: >- One key: a random alphanumeric value of `length` characters (16 to 64, default 32), or the fixed `value` the chart is told to use, never both. properties: key: type: string length: type: integer minimum: 16 maximum: 64 value: type: string maxLength: 63 securitySchemes: BearerAuth: bearerFormat: PAT scheme: bearer type: http ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.