Skip to main content

Sources

A source is where your application comes from. You pick it on the Source step when you deploy an application, and everything else about the application works the same whichever source you pick.

Start with a container image for a web service. AstroPulse writes the Kubernetes setup for you, including scaling and placement. Choose a Helm chart, a Git repository or YAML only when you already package your application that way.

Choose a source​

You haveUseWhat AstroPulse does
A container imageContainer imageRuns it as a web service, sized and placed by its availability tier.
A chart in a Helm or OCI repositoryHelm chartInstalls the chart with your values.
A Helm chart in a Git repositoryGit repositoryInstalls the chart from the branch, tag or commit you pin.
Kubernetes manifestsYAMLApplies them as written, operators and custom resources included.
An AI modelServe a modelServes it, and tells you when it is ready to call.

The source cannot be changed once the application exists. To switch sources, deploy a new application.

After you deploy​

Every application, whatever its source, has the same page in the console under Workloads > Applications:

  • Overview shows its status, endpoint, spend and security findings.
  • Events and Logs show what happened and what it printed. See Troubleshoot.
  • Update changes its configuration, resyncs it, or rolls it back to an earlier version. See Releases and rollback.
  • Delete removes it from its cluster. Deleting needs the admin role in your organization.

Settings every application shares​

The wizard asks for these whichever source you choose. Each card shows the console's name for it, then its key in a manifest:

Application namenameRequired

The application's name, unique in your organization.

Accepts
1 to 50 characters: lowercase letters, numbers and hyphens.
ProfileprofileNameRequired

The application profile it deploys through, which picks its cluster. Fixed once the application exists.

Accepts
The name of a profile in your organization.
Namespace (Options step)namespace

The Kubernetes namespace it runs in. A namespace you name is yours: AstroPulse creates it if it does not exist, deploys into it beside whatever else lives there, and never deletes it, so several applications can share it. Fixed once set.

Accepts
A valid Kubernetes namespace name, up to 63 characters.
Default
A namespace named after the application, which belongs to that one application.
Sync Type (Options step)syncType

Whether AstroPulse keeps the cluster matching the source. With Automatic, a change on the Git branch or chart the source points at reaches the cluster on its own. Set Manual only to pause that while you test on a live cluster, and set it back afterwards: while it is Manual, changes do not reach the cluster.

Accepts
  • Auto Automatic Changes to the application's spec deploy on their own, and drift on the cluster is corrected.
  • Manual Manual Changes deploy only when you resync the application; for testing on a live cluster.
Default

Auto

External access (Access step)externalAccess

How the application is reached from outside the cluster, for image and model applications. Leave it out for an application only the cluster can reach.

With astroctl​

Terminal
astroctl app apply -f application.yaml --dry-run # check it; deploys nothing
astroctl app apply -f application.yaml
astroctl app delete -n <app-name>

See the astroctl reference.

Next​