Repository navigation
feat(netbird)!: remove MySQL support; bump netbird to 0.82.0 - #156
Merged
Merged
Conversation
NetBird 0.82.0 removed its MySQL store: a management server configured with the mysql engine refuses to start. A plain appVersion bump would have left every database.type=mysql install with a crashlooping server. Instead the chart now fails at template time for database.type=mysql, printing the migration path (stay on chart 0.7.x / NetBird 0.81.x, run netbird-mysql-migrate from v0.81.5, switch to postgresql, then upgrade). Unknown database.type values are rejected the same way; only sqlite and postgresql are accepted. The mysql DSN/port branches, unit tests, e2e scenario, CI job, make target, e2e values, and seed example are removed; README replaces the MySQL install example with a migration section. Also bumps: - appVersion 0.81.3 -> 0.82.0 (also covers 0.81.4/0.81.5). Access logs now use their own store connection, defaulting to access_logs.db next to the SQLite store or the main DSN on PostgreSQL — no change needed. Combined-server config template and dashboard env contract are byte-identical to 0.81.3 upstream. - dashboard image v2.95.0 -> v2.96.0. BREAKING CHANGE: database.type=mysql is rejected; migrate to PostgreSQL on chart 0.7.x before upgrading (steps in CHANGELOG.md). Closes #153, #154, #155 Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This was referenced Oct 31, 2026
mikkeldamsgaard
added a commit
that referenced
this pull request
Oct 31, 2026
- Bump chart version 0.7.2 -> 0.8.0 - appVersion 0.82.0, dashboard image v2.96.0 - Refresh compatibility matrix: chart 0.8 verified against server 0.82.0, 0.81.5, 0.80.0, 0.79.0, 0.78.2 — all PASS Contains a breaking change (#156): database.type=mysql is rejected because NetBird 0.82.0 removed its MySQL store. Released as a minor rather than 1.0.0 because the chart is pre-1.0 (same as 0.7.0); migration steps are in CHANGELOG.md. Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Folds in #153, #154, #155 (netbird 0.81.3 → 0.82.0). This is not a plain version bump.
From the v0.82.0 release notes: "A management server configured with the
mysqlengine refuses to start on v0.82.0." Thenetbird-mysql-migratetool is no longer shipped either. Bumping appVersion alone would have left everydatabase.type: mysqlinstall with a crashlooping server afterhelm upgrade.So this PR:
database.type: mysql, printing the migration path: stay on chart 0.7.x (NetBird 0.81.x), runnetbird-mysql-migratefrom v0.81.5, switch topostgresql, then upgrade. This matches the chart's existing fail-fast guards. Unknown types (e.g.mariadb,"") are rejected too; onlysqliteandpostgresqlpass.make e2e-mysqltarget + e2e values, andexamples/seed/mysql-values.yaml.Marked
!/BREAKING CHANGE. For the release I'll follow the 0.7.0 precedent: a minor bump (0.8.0) for a breaking change on this pre-1.0 chart, with a regenerated compat matrix.Version bumps
render_combined_yamlandrender_dashboard_envare byte-identical between 0.81.3 and 0.82.0. The new dedicated access-log store defaults toaccess_logs.dbbeside the SQLite store (on the existing PVC) or the main DSN on PostgreSQL, so nothing changes on upgrade. 0.81.4 distrusts the compromised eMudhra CA keys.Keycloak MySQL support is untouched; Keycloak itself still supports it.
Closes #153, #154, #155
How to verify
🤖 Generated with Claude Code