Skip to content

Upgrade MySQL from 8.0 to 8.4 LTS (step 2)#69

Merged
nesono merged 2 commits intomainfrom
upgrade/mysql-8.0-to-8.4-lts
Mar 28, 2026
Merged

Upgrade MySQL from 8.0 to 8.4 LTS (step 2)#69
nesono merged 2 commits intomainfrom
upgrade/mysql-8.0-to-8.4-lts

Conversation

@nesono
Copy link
Copy Markdown
Owner

@nesono nesono commented Mar 28, 2026

Summary

  • Upgrades mysql_mail and mysql_wordpress_noerpel from MySQL 8.0 to 8.4 LTS (supported until April 2032)
  • Adds --mysql-native-password=ON to preserve auth compatibility with existing clients
  • Disables healthchecks during migration to prevent premature container restarts

Pre-deployment checklist

  • Back up mysql_mail_data volume
  • Back up mysql_wordpress_noerpel_data volume
  • Confirm step 1 (5.7 → 8.0) is deployed and stable

Post-deployment verification

  • Both MySQL containers start without errors (docker compose logs mysql_mail)
  • Dovecot/Postfix/Postfixadmin connect successfully
  • WordPress connects successfully
  • Re-enable healthchecks once migration is confirmed stable

Follow-up

  • Migrate users from mysql_native_password to caching_sha2_password
  • Remove --mysql-native-password=ON flag
  • Re-enable healthchecks
  • Configure Renovate to only allow patch updates within 8.4.x

🤖 Generated with Claude Code

nesono and others added 2 commits March 28, 2026 14:16
Second step of the safe migration path: 5.7 → 8.0 → 8.4 LTS.
MySQL 8.4 is the current LTS release (supported until April 2032).

- Enable --mysql-native-password=ON since 8.4 disables it by default;
  existing clients (dovecot, postfix, postfixadmin, WordPress) still
  use the old auth plugin. Users should be migrated to
  caching_sha2_password in a follow-up.
- Disable healthchecks during migration to prevent premature container
  kills while the upgrade runs.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@nesono nesono merged commit 0793f91 into main Mar 28, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant