Regular Software Updates¶

• Table of contents
• Regular Software Updates
  • Kubernetes based Applications
    • ArgoCD
    • gitea 1.19.x to 1.20.x upgrade
    • gitea 1.20.x to 1.21.x upgrade

There are various software stacks that should be updated regularly. This document describes the intervals and procedures.

Kubernetes based Applications¶

All kubernetes based applications should be updated in a 2 step manner:

• Create a ticket in the datacenterlight project for the update
• Create or update apps/dev/APPNAME in k8s-config
• Create or update a test instance in the kubernetes cluster that is using apps/dev/APPNAME
• Ensure the test instance is running properly
• Apply changes from apps/dev/APPNAME to apps/prod/APPNAME
• Ensure all production instances are applying and working properly

Schedule: all apps should be checked for new updates at least once per month.

ArgoCD¶

We usually use stable via:

kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml

gitea 1.19.x to 1.20.x upgrade¶

• need to modify /data/gitea/conf/app.ini

Deprecated config option `[mailer]` `MAILER_TYPE` present. Use `[mailer]` `PROTOCOL` instead. This fallback will be/has been removed in v1.19.0 (and 1 more)

Deprecated config option `[mailer]` `HOST` present. Use `[mailer]` `SMTP_ADDR` instead. This fallback will be/has been removed in v1.19.0

gitea 1.20.x to 1.21.x upgrade¶

• need to modify /data/gitea/conf/app.ini
• See https://docs.gitea.com/administration/logging-config

Deprecated config option `[log]` `ROUTER` present. Use `[log]` `logger.router.MODE` instead. This fallback will be/has been removed in 1.21 (and 2 more)