Maintainer | GitHub ID | Affiliation |
---|---|---|
Idan Levy | idanl21 | Opster |
Ido | ido-opster | Opster |
Dan Bason | dbason | SUSE |
Sebastian Woehrl | swoehrl-mw | MaibornWolff |
Prudhvi Godithi | prudhvigodithi | Amazon |
This document explains what maintainers do in this repo, and how they should be doing it. If you're interested in contributing, see CONTRIBUTING.
This guide will explain the new version release process in Opensearch-k8s-Operator
Under the relases process we can find two main actions
- ####Operator release Responsible to build and publish new Opensearch-k8s-operator images, builds from the 'release.yaml' workflow that triggers from new tag creation with 'v' prefix.
- ####Helm release
Respoinsable for Helm chart repo update, will set helm chart version to version from tag and will Run action to build chart and publish it to a new release and update the index in the
gh-pages
branch, will also publish version to Artifacthub. builds from the 'helm-release.yaml' workflow that triggers from new tag creation with 'helm' prefix.
###Steps So for a release we need the following manual steps:
- Create a new tag "vX.Y.Z"
- Wait until pipeline is finished
- Create a new tag "helm-X.Y.Z"