KUSANAGI 8, which is based on CentOS 7, scheduled to reach its end of life at the end of July 2024, as CentOS 7 will no longer be supported by the community by June 30, 2024.
As for the KUSANAGI 8 instances that have already been deployed, there will be no impact from the cloud side after the end of the availability, and our KUSANAGI RPM repository will remain for the time being, so they can continue to be used as is.
However, CentOS 7 will not be supported by the community after June 30, 2024, and we will not update the KUSANAGI RPM repository after KUSANAGI 8 reaches its end of life.
Therefore, from a security perspective, please consider migrating to KUSANAGI 9 on AlmaLinux OS 8 or other OS* as soon as possible.

*Migration to

• KUSANAGI 9 on AlmaLinux OS 8
• KUSANAGI 9 on AlmaLinux OS 9

How to check and migrate KUSANAGI 8

# kusanagi status

For KUSANAGI 8 (* version numbers may vary):
KUSANAGI Version 8.7.13-1

For KUSANAGI 9 (* version numbers may vary):
KUSANAGI Version 9.4.14-1.el8

End of support for CentOS 7

• Improves WordPress (and other CMS) speed and stability
• Performance guarantee for the latest WordPress
• Update modules via repository until CentOS7 EOL
• Compatible with newest major instance types
• Module updates via KUSANAGI
• Middleware updates via KUSANAGI
• Packaged with KUSANAGI-specific plugins
• WordPress, concrete5, Drupal7, Drupal8 provisioning via commands
• Database-switch feature (MariaDB/PostgreSQL)
• Japanese search feature (mroonga)
• WAF (nginx:NAXSI Apache:ModSecurity)
• WordPress WAF (included with KUSANAGI) signature updates
• IDS (tripwire)
• IDS/IPS (suricata)
• Vulnerability scanning tool (vuls)
• Let's Encrypt
• SELinux compatibility
• monit