Skip to main content
Thoras ships continuously. Within a single major version (for example 5.x.x), minor and patch releases are routine and should not require any special steps. A major chart version bump (for example 4.x.x to 5.x.x) signals a breaking change that may need human intervention. Only one major version can be crossed at a time (for example, 4.x.x to 6.x.x is not supported). The authoritative, step-by-step migration notes for every major version live in the chart repository:

UPGRADE.md on GitHub

Detailed upgrade procedures for each breaking chart release.

​
Chart 5.x at a glance

Chart 5.0 adds dashboard authentication and moves credential management into the cluster. Most 4.x installs upgrade with no changes to values.yaml.
  • The dashboard requires a login. An oauth2-proxy sidecar now fronts the dashboard, using a generated username and password by default or your identity provider via OIDC. See Dashboard authentication.
  • Credentials are managed in-cluster. A new thoras-config-controller component seeds any credential you don’t supply, migrates your existing 4.x credentials automatically, and restarts dependent workloads when a credential changes. See Credentials.
  • featureFlags.enableSimpleAuthSecret is renamed to apiClientSecret.enabled. The old name still works as an alias. See Deprecations.

​
Does anything apply to me?

Work through whichever of these match your deployment:
If you use the chart’s legacy secret seeding (the 4.x default), complete the upgrade with featureFlags.enableLegacySecretSeeding left at its default of true so the config-controller can migrate your existing credentials. Once all pods are healthy, set it to false.