Make supplementary services versions automatically taken into release chart #254
Description
Is your feature request related to a problem? Please describe
No response
Describe the solution you'd like
Currently release process working just fine, but we need an additional feature to make it more user friendly and reliable.
For supplementary service, like Disaster Recovery Daemon and Status Provisioner, we pass specific versions during release by hands.
We want to get rid of this process, so any supplementary service release versions would be taken automatically during release process via github actions.
Current approach:
SP and DRD versions are taken as variables., which had been passed during job invocation.
https://github.com/Netcracker/qubership-opensearch/blob/main/.github/helm-charts-release-config.yaml
What we want:
Make versions be configurable and taken automatically:
- ghcr.io/netcracker/qubership-disaster-recovery-daemon:v4.x.x
- ghcr.io/netcracker/qubership-deployment-status-provisioner:0.x.x
For instance, during 2.2.0 release of Kafka, latest release versions for DRD and SP are v.4.5.6 and 0.9.1, so these versions will be taken for THIS concrete release and then passed to the values.yaml file as necessary services versions.
In addition, i suggest to make latest version, for which necessary logic will understand, that required version is the lates release of supplementary service should be taken, following is an example in case v4.5.6 is the latest
ghcr.io/netcracker/qubership-disaster-recovery-daemon:latest -> ghcr.io/netcracker/qubership-disaster-recovery-daemon:v4.5.6
Describe alternatives you've considered
No response
Additional information
No response
Metadata
Metadata
Assignees
Type
Projects
Status