From 545410767f32888e7e4d9db8b17c26671db73b50 Mon Sep 17 00:00:00 2001 From: Clemens Date: Tue, 9 Jul 2024 09:05:57 +0200 Subject: [PATCH] Added runbook todo and disabled forgejo-federated-image-publish --- .gitlab-ci.yml | 13 +++++++------ ...To7.0.5.md => Runbook_UpgradeFrom1.19To7.0.5.md} | 6 ++++-- 2 files changed, 11 insertions(+), 8 deletions(-) rename doc/{Playbook_UpgradeFrom1.19To7.0.5.md => Runbook_UpgradeFrom1.19To7.0.5.md} (98%) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 79ff9ac..a52445c 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -123,9 +123,10 @@ forgejo-backup-image-publish: script: - cd infrastructure/backup && pyb image publish -forgejo-federated-image-publish: - <<: *img - <<: *tag_only - stage: image - script: - - cd infrastructure/federated && pyb image publish \ No newline at end of file +# This is currently not needed +#forgejo-federated-image-publish: +# <<: *img +# <<: *tag_only +# stage: image +# script: +# - cd infrastructure/federated && pyb image publish \ No newline at end of file diff --git a/doc/Playbook_UpgradeFrom1.19To7.0.5.md b/doc/Runbook_UpgradeFrom1.19To7.0.5.md similarity index 98% rename from doc/Playbook_UpgradeFrom1.19To7.0.5.md rename to doc/Runbook_UpgradeFrom1.19To7.0.5.md index cc29c85..914f919 100644 --- a/doc/Playbook_UpgradeFrom1.19To7.0.5.md +++ b/doc/Runbook_UpgradeFrom1.19To7.0.5.md @@ -59,6 +59,8 @@ ## Upgrade to 7.0.5 (no breaking changes) +TODO: Upgrade to 8.0.0 instead after Release! + 1. Scale down Forgejo Deployment: `k scale deployment forgejo --replicas=0` 1. Delete app.ini: `k exec -it backup-restore-... -- rm /var/backups/gitea/conf/app.ini` 1. Set version to `7.0.5` with `k edit deployment forgejo` @@ -74,9 +76,9 @@ 1. The scope of all access tokens might (invisibly) have changed (in v1.20). Thus, rotate all tokens! 1. Users should check their ssh keys: if they use rsa keys the minimum length should be 3072 bits! However, shorter keys should still work. -# Known Errors +## Known Errors -## Error in v1.20.1-0 +### Error in v1.20.1-0 In the logs the following error can be found. This will be resolved automatically with the next upgrade (v1.21).