Build from source
Package a Helm chart from your GitHub repository. Charts are stored on Ryvn’s Registry.Use public charts
Deploy public Helm charts from chart repositories.Use private charts
Deploy Helm charts from private registries. First, connect your private registry through Settings in the Ryvn Dashboard, then reference it by name.Properties
name
string — required
Service identifier. Must be lowercase, alphanumeric with hyphens only.
labels
object — optional
Key-value labels for grouping and filtering services. Use labels to organize services by team, tier, or any other dimension.
Constraints:
- Maximum 50 labels per service
- Keys must start with an alphanumeric character and contain only alphanumerics, dots, hyphens, and underscores
- Keys and values are each limited to 63 characters
type
string — required
Must be helm-chart.
repo
string — required
GitHub repository (owner/repo) when packaging from source, or chart
repository URL when using public charts.
chart
string — conditional
Chart name in the repository. Required for public charts. If not specified
when building from source, defaults to service name.
registry
string — optional
Registry name for storing built charts. Defaults to Ryvn’s built-in registry
when building from source. With a connected private registry bound, built
charts are pushed there using the registry’s credential (or its dedicated
publish credential); create the chart repository ahead of time.
promotionPipeline
string — optional
Name of promotion pipeline to follow for automated release promotion.
maintenanceWindow
string — optional
Maintenance window for this service. Automated deployments will only occur during specified intervals.
build.chartPath
string — required
Path to directory containing Chart.yaml, relative to repository root. Required
when building from source.
build.branches
array — optional
List of branches that trigger helm chart builds and releases on push. Each
entry has a name and optional args (build arguments specific to that
branch). When configured, pushing to any listed branch packages and releases
the chart automatically. Installations can then track a specific branch using
the branch field. Only applies when building from a GitHub repository, not
when using public or private chart registries.
Compatible with promotionPipeline, but a branch release channel can only
appear once in a pipeline.