| ... | ... | @@ -45,7 +45,7 @@ |
|
|
|
* you have changed only configuration files of the [kypo-crp-head](https://gitlab.ics.muni.cz/muni-kypo-crp/devops/kypo-crp-helm/-/tree/master/helm/kypo-crp-head) chart in [kypo-crp-helm](https://gitlab.ics.muni.cz/muni-kypo-crp/devops/kypo-crp-helm) project, skip step 3.
|
|
|
|
* you have changed tag/s and configuration files, don't skip any steps.
|
|
|
|
|
|
|
|
2. Make sure that you have set the **kypo-crp-head** chart version properly with release candidate suffix. Whenever you are changing the configuration files of **kypo-crp-head** chart (except the image tags) increase only the release candidate version. Then set the variable `kypo_crp_head_version` in the file [muni-kypo-tf-kypo-crp/tfvars/stage.tfvars](https://gitlab.ics.muni.cz/muni-kypo/deployment/terraform/muni-kypo-tf-kypo-crp-kubernetes/-/blob/master/tfvars/stage.tfvars) to be the same as in the release branch.
|
|
|
|
2. Make sure that you have set the **kypo-crp-head** chart version properly with release candidate suffix. Whenever you are changing the configuration files of **kypo-crp-head** chart (except the image tags) increase only the release candidate version. Then set the variable `kypo_crp_head_version` in the file [muni-kypo-tf-kypo-crp/tfvars/stage.tfvars](https://gitlab.ics.muni.cz/muni-kypo/deployment/terraform/muni-kypo-tf-kypo-crp-kubernetes/-/blob/master/tfvars/stage.tfvars) to be the same as in the release branch. **Keep in mind** that while using release candidate versions `helm_repository` suffix has to be set to `/devel`. On the other hand, using a stable version requires the usage of `/stable` suffix.
|
|
|
|
|
|
|
|
3. Make sure that all versions of [microservices charts](https://gitlab.ics.muni.cz/muni-kypo-crp/devops/kypo-crp-helm/-/tree/master/helm/kypo-crp-head/charts) are updated and propagated to the [stage.yaml](https://gitlab.ics.muni.cz/muni-kypo/deployment/terraform/muni-kypo-tf-kypo-crp-kubernetes/-/blob/master/value-files/stage.yaml) file.
|
|
|
|
|
| ... | ... | |
