Upgrading Gitea from 1.23.5 -> 1.24.3

Gitea and related runners were waiting for an upgrade! There were a lot of changes between 1.23.5 and 1.24.3, along with several helm charts being released.

Valkey Introduction

Gitea’s chart moves from redis to Valkey. Since I run scaled down Redis charts this was a bit of a problem. Valkey is an open source fork of Redis 7.2.4 which has continued to evolve.

I went for the standalone Valkey setup to tune down for my small instance use case. I’m guessing the cluster chart can be found here.

Following was how I got the service booted.

valkey-cluster:
  enabled: false
valkey:
  enabled: true
  global:
    defaultStorageClass: "longhorn"

I had to manually turn off the old Redis cluster serving Gitea. This was an artifact of using my own configuration for tiny runs.

Failed Migrations

I encountered a failed migration related to UQE_secret_owner_repo_name. Gitea has moved to setting all owner_id to 0. Appears to be an issue with instances living since 1.22. This change manually forces all secrets to be a repository secret from my scanning.

Conclusion

Been a while since I had to jump into Postgres to resolve an issue.

In the future I need to spend time learning how to hint about pod co-location. Gitea and Valkey were scheduled to different machines in my test.