From 5573659091792adbe6e83c6efd9324e6c9bc782e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Rok=20Ro=C5=A1kar?= Date: Tue, 3 Dec 2024 19:03:08 +0100 Subject: [PATCH] chore: add note about removing gitlab values --- helm-chart/values.yaml.changelog.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/helm-chart/values.yaml.changelog.md b/helm-chart/values.yaml.changelog.md index d65846f1c..d559ad49e 100644 --- a/helm-chart/values.yaml.changelog.md +++ b/helm-chart/values.yaml.changelog.md @@ -5,6 +5,10 @@ For changes that require manual steps other than changing values, please check o Please follow this convention when adding a new row * ` - **:
` +## Upgrading to Renku 0.62.0 + +* DELETE ``gitlab.*`` - all values related to the bundled GitLab have been removed. GitLab must from now on be provided as an external service and is no longer supplied as a part of the Renku Helm chart. + ## Upgrading to Renku 0.61.0 * NEW ``networkPolicies.allowAllIngressFromPods`` specify pod selectors that will allow the selected pods to access all other services in the Renku release namespace. @@ -78,7 +82,7 @@ New (either `running`, `finished` or `errored`) for the overall state of the rotation. Please make sure to unset `secretServicePreviousPrivateKey` once rotation is finished as a matter of best practice. - NOTE: Make sure that you do not redeploy or rollback the Renku Helm chart while a key rotation is underway. Even if the + NOTE: Make sure that you do not redeploy or rollback the Renku Helm chart while a key rotation is underway. Even if the deployment is broken it is best to wait for the key rotation to finish before attempting another deployment or a rollback. ## Upgrading to Renku 0.53.0