Skip to main content

YAML

Apply the Kubernetes manifests in a folder of a GitHub repository, exactly as written. Use it for anything that is already plain manifests: an operator, custom resources, or a service you describe yourself. AstroPulse keeps the cluster matching the branch, so a push reaches the cluster on its own. No manifests yet? Ask Nova to write them for your service, then push them to the repository.

Before you start​

In the console​

  1. Open Workloads > Applications > Deploy application. Enter the Application name and pick the Target Cluster.

  2. On Profile, keep the profile picked for the cluster, or select Create New.

  3. On Source, select YAML manifests. Enter the Repository URL, for example https://github.com/astropulseinc/latency-app.git. Browse beside it opens your connected repositories on the GitHub page in a new tab.

  4. Enter the Branch / Tag, for example v1.1.0. A tag pins the manifests; a branch follows every push.

  5. Under Path to YAML Directory, enter or Browse to the folder, for example k8s, then select Validate: it checks YAML files exist at that path.

    Open zoom view

    The Source step with YAML manifests: a GitHub repository, its tag and the manifests folder

    The Source step with YAML manifests: a GitHub repository, its tag and the manifests folderThe Source step with YAML manifests: a GitHub repository, its tag and the manifests folder
  6. Optional: on Files, turn off Search Recursively to read only the folder itself, or narrow the files with Include Pattern (for example *.yaml,*.yml) and Exclude Pattern (for example *.md).

  7. Select Review, run the dry run, then Deploy.

You should see​

The application's page in Workloads > Applications shows Running once its resources are up, with events and logs.

Open zoom view

An application's Overview with its running configuration

An application's Overview with its running configurationAn application's Overview with its running configuration

If it does not start, its Events and Logs tabs say why: Troubleshoot.

How changes reach the cluster​

With Sync Type Automatic (the default, on the Options step), a push that changes the manifests reaches the cluster on its own, within 3 to 5 minutes. A tag or a commit SHA never moves, so nothing changes until you point the application at a new one from its Update tab. A synced push is not a version: AstroPulse records a version only when it applies the application, such as an apply from the Update tab, and only versions can be rolled back to. History lists those versions, with drift, self-heal and failed syncs shown without a version number.

When you delete a manifest from the folder, AstroPulse removes it from the cluster. With Sync Type Manual, that happens when you next apply or resync.

What AstroPulse applies​

Every manifest the folder and patterns select, as written: AstroPulse does not add scaling, placement or exposure to them. Set replicas, resources and an Ingress or Service in the manifests themselves. The Access step and Custom domain apply to image and model applications.

Other ways in​

  • Nova: ask it to deploy the manifests from your repository, or to write them for your service.
  • SDK and API: the same manifest: Deploy an application.

With astroctl​

application.yaml
apiVersion: platform.astropulse.io/v1
kind: Application
spec:
name: latency-yaml
profileName: default-profile
source:
type: YAML
yaml:
repo:
repoURL: https://github.com/astropulseinc/latency-app.git
targetRevision: v1.1.0
path: k8s
recursive: true
include: "*.yaml,*.yml"
Terminal
astroctl app apply -f application.yaml --dry-run
astroctl app apply -f application.yaml

See the astroctl reference.

Settings​

The settings every source shares (name, profile, namespace, sync) are on Sources. These are specific to YAML:

Repository URLsource.yaml.repo.repoURLRequired

The GitHub repository. A private one is read through the GitHub integration.

Branch / Tagsource.yaml.repo.targetRevisionRequired

The branch, tag or commit SHA to apply. A branch follows every push; a tag or SHA stays fixed.

Path to YAML Directorysource.yaml.repo.pathRequired

The folder with the manifests, relative to the repository root.

Search Recursivelysource.yaml.recursive

Read the folders inside the path too.

Default
true
Include Patternsource.yaml.include

Only the files that match, as comma-separated patterns.

Accepts
For example *.yaml,*.yml.
Exclude Patternsource.yaml.exclude

Files to leave out, as comma-separated patterns.

Accepts
For example *.md.

If it's refused​

GitHub Integration Required for Private Repositories: "If this is a private repository, you need to set up GitHub integration first."
Cause
The repository is private and not connected, so its folders cannot be read.
Fix
Connect it under Integrations > GitHub, then pick the folder again.
"Path is required"
Cause
No folder is set under Path to YAML Directory.
Fix
Pick the folder with Browse.

Next​