AI Software Templates Helm Charts

This project aims to convert the AI Software Templates functionality into helm charts. Therefore, it aims to reproduce the flow of AI Software Templates without the usage of RHDH.

Available Helm Charts

At the moment one template has helm chart support and this is the chatbot application template. The chatbot helm chart can be found here.

Gitops

The gitops component, handled by ArgoCD for the RHDH case, is replaced by a Kubernetes Job created by the Helm chart, where this Job:

• Creates the GitHub repository for the application.
• Copies the application source code into the new repository.
• Copies the Tekton Pipelines As Code PipelineRun/Pipeline/Task that build new images for the application as pull requests are merged and updates the Deployment of the application with the new version of the image.
• Commits these changes and pushes the commit to the preferred branch of the new repository.

The source code is here.

OpenShift Pipelines

For OpenShift Pipelines configuration there's an OpenShift Pipelines Configuration Guide that the user can follow to configure their pipelines, prior to installing the helm chart.

The helm chart mainly uses the tekton pipelines under rhdh-pipelines repo. The only customized resources used for the helm chart case are:

• The .tekton/docker-push.yaml PipelineRun used to manage push events received from the github app webhook.
• The update-deployment.yaml Task which is used to update the application deployment whenever a new image is pushed to the image registry.
• The docker-build-ai-software-templates-chart.yaml Pipeline, again used for the application deployment update.

Testing with a Custom Helm Repository

To test your updates by importing the ai-lab-helm-charts fork as a custom Helm chart repository, you can follow the instructions here

Release Process

The ai-lab-helm-charts are created on demand.

• A tag should be created with the version of the release as the name. ai-lab-helmcharts follows the v{major}.{minor}.{bugfix} format (e.g v0.1.0).
• Before proceeding, make sure that all the version fields within Chart.yaml have this tag as the value. For example in the case where the tag is v0.1.0, the version should be 0.1.0.
• After the new release is published, the updated Helm packages will be pinned on the release.