Charts provide a way to define, package, and deploy complex Kubernetes applications using Helm. They offer complete control over your Kubernetes resources with integrated release management and rollback capabilities. Understanding Kubernetes basics is recommended for working with charts.

Custom Domains

To configure custom domains, ingress controllers, and TLS certificates for your Helm charts, see the Custom Domains documentation. This covers:

  • Configuring ingress for public and internal services
  • Using Ryvn’s built-in NGINX controllers (external-nginx and internal-nginx)
  • Automatic TLS certificate management
  • DNS configuration for custom domains

Versioning

Helm chart versions in Ryvn directly correspond to service release versions. When you create a release for your chart service, the release version must match an existing chart version in your repository.

For GitHub-hosted charts:

  • Chart versions are defined in Chart.yaml (version field)
  • Release versions should match the chart version you want to deploy
  • Ryvn will look for the chart at the specified version in your repository

For public chart repositories:

  • Chart versions are managed by the chart maintainer
  • You must use versions that actually exist in the public repository
  • Check the chart repository’s available versions before creating releases

Public Charts

Public charts allow you to deploy community-maintained or vendor-provided Helm charts without hosting your own chart repository.

Deploying a Public Chart

1

Create Chart Service

  1. Navigate to Services and click Create Service

  2. Select Helm Chart as the service type

  3. Choose Deploy from Public Chart

  4. Provide the required information:

    Repository URL: The Helm repository URL

    • e.g., https://charts.bitnami.com/bitnami

    Chart Name: The name of the chart in the repository

    • e.g., postgresql
2

Create Service Releases

  1. Go to your chart service and click Create Release

  2. Version must match exactly what the chart maintainer published

    For example, if the chart has versions 12.1.2, 12.1.1, 12.1.0, you must use these exact versions

3

Deploy to Environment

  1. Navigate to your target environment
  2. Click Add Service and select your public chart service
  3. Choose the release version you want to deploy
  4. Configure values specific to this installation

Troubleshooting