Applications / Template

Model / API keys endpoint

GitHub example manifest: applications/model/api-keys-endpoint.yaml

Overview

This example is available in the AstroPulse GitHub template repository. Review its manifest and deployment requirements before applying it.

Category
Applications
Source
applications/model/api-keys-endpoint.yaml

This manifest was discovered from GitHub. Detailed prerequisites and commands have not been curated yet; do not assume it is ready for direct deployment.

Prerequisites & dependencies

Prerequisites have not been documented for this GitHub example. Inspect the manifest before use.

No dependencies are listed in the available catalog metadata. This is not a guarantee that none are required.

Source manifest

applications/model/api-keys-endpoint.yaml

# A model on your domain, callable with an API key
#
# Served at https://qwen-chat.example.com through the gateway. Callers send a
# key from the access policy access-policies/api-keys.yaml; a request without
# one gets HTTP 401.
#
# Before you apply:
#   - everything gpu.yaml needs
#   - example.com verified under Integrations > Domains
#   - the gateway add-on, cert-manager with a DNS solver
#     (add-ons/cert-manager-letsencrypt-dns.yaml) and, to publish the DNS
#     record, external-dns with gatewayRoutes: true
#   - the access policy: astroctl access-policy apply -f access-policies/api-keys.yaml
#
# Apply:  astroctl app apply -f api-keys-endpoint.yaml --dry-run, then without --dry-run
# Keys:   astroctl access-policy key create partner-keys --label partner-a
apiVersion: platform.astropulse.io/v1
kind: Application
spec:
  name: qwen-chat
  profileName: <YOUR_PROFILE_NAME>
  source:
    type: Model
    model:
      uri: hf://Qwen/Qwen3-8B
      resources:
        accelerator:
          gpu:
            model: l4
            countPerReplica: 1
      scaling:
        minReplicas: 1
        maxReplicas: 4
  externalAccess:
    domain: example.com               # served at qwen-chat.example.com
    exposure: Public
    accessPolicyRef:
      name: partner-keys

Deployment guidance

Go straight to Console to create clusters, deploy applications, and manage supported resources. Templates and CLI commands are optional; not every GitHub manifest has an automatic import path.

Console — start directly

Open Console to create or connect infrastructure and deploy applications without running astroctl or copying this YAML first. This template may still require manual setup.

Open Console

astroctl

No verified CLI sequence is published for this example. Review the source and the onboarding guide rather than running a guessed command.

Get Started

Nova

Prefer to describe the goal? Ask Nova to review this example and help plan supported actions. Access, policy, and approvals still apply.