Last week Tuesday Magento 2.4 was released, since then we have updated our Magento 2 preinstall (and sample data) to use this new version. With this new version some system requirements have changed: for the first time we will now enable ElasticSearch (version 7.6.x) by default on nodes that request a preinstallation of Magento. While it is still technically possible to install Magento 2.4 without a working ElasticSearch, you will encounter errors if you try to do anything meaningful when the correct version is not configured.

Also the MySQL version that will be used when Magento is selected as a preinstall on Hypernode has been changed from MySQL 5.6 to 5.7. Note that in this new Magento 2.4 version MySQL 8 and PHP 7.4 are now newly supported for the first time and can be selected using the hypernode-systemctl command-line tool or using the API.

In other news, the hypernode-fpm-slow-modules tool can also be used for Magento 2.

Thanks to Lewis Voncken from Experius for figuring this one out.

Other changes:
– We had some trouble with creating new floating IPs at certain DigitalOcean regions like nyc1, nyc2 (not nyc3) and tor1. This was due to DigitalOcean changing their network to a layer 3 set-up gradually over all their regions. This issue has for now been resolved with a work-around by configuring a static ARP entry for the anchor gateway IP allowing us to boot droplets in those regions again.
– Fixed a bug in the Service Panel importer that caused it to fail if the session-bound generated SSH key was used instead of a password.
– Various hypernode-managed-vhosts tweaks and fixes
– Fix active FTP on Buster, net.netfilter.nf_conntrack_helper was not enabled while it had been on Xenial
– The MVG ImageMagick image coder is now allowed on Buster
– Extra CRON jitter, but this time for system crons. This should improve fleet-wide performance somewhat.