As foreshadowed in the Lagoon 2020 roadmap, native Kubernetes support was always going to feature large in the first half of this year – we got a large portion of the work done in our Austin sprint and this is the release of that (and some follow-up) work.
Rest assured that we’re still working on features and fixes for the Openshift components (the two can exist side-by-side quite happily for now). As we develop new features, we will take into consideration compatibility with both platforms.
Vanilla Kubernetes support - Lagoobernetes
- The headlining act for 1.4.0 is the release of Kubernetes compatibility for Lagoon. Currently, this is supported for configurations where Lagoon deploys from a central Openshift into a Kubernetes cluster.
- Full Kubernetes support in Lagoon will need some adaptations and changes in the Lagoon API, these will happen in Lagoon 2.0.0.
- Lagoon on Kubernetes has been tested extensively against most versions of managed Kubernetes (Azure Kubernetes Service – AKS, Amazon Elastic Kubernetes Service - EKS, and Catalyst Cloud), with more to come.
- Despite this, 1.4.0 being the first official Kubernetes-compatible release, this code is already running in production for two of our customers - and we’re really happy with how it’s going - Michael ran through the process in his recent webinar!
Other changes in this release
- Even though this release is primarily about releasing Kubernetes compatibility, there are a number of other smaller fixes, updates and inclusions coming.
API & Authentication subsystem
- A long-running issue has been with the deletion of environment variables – and we’ve fixed it now. Also coming in this release is the ability to execute a `drush uli` as a task via the UI or CLI – this will currently only work for UID 1, and only if it’s unblocked.
Build & Deploy subsystem
- 1.4.0 introduced the ability to specify production environments as active or standby – this is the precursor to being able to implement a blue-green deployment approach – expect to hear more about this once the rest of the implementation lands.
- There’s a couple of minor issues we’ve come across that have now been fixed.
Logging & Reporting subsystem
- As more Kubernetes clusters are being rolled out across different providers, we needed to add more plugins to store ElasticSearch indexes.
Base Images & Testing subsystem
- A couple of small updates here to the bundled versions of Composer and New Relic, as well as updating our tests to use Drupal 8.8.4
Documentation & Examples / DX subsystem
- As always, more minor fixes and updates to documentation.
Automation, Services & Helpers subsystem
- This release brings the backup handler into Lagoon, to ensure that it releases at the same cadence as the other components – the backup handler controls the scheduling, creation, availability and restoration of the automated backups.
- The database operator released in Lagoon 1.3.0 has been upgraded for use with Kubernetes and also made more generic to support multiple database backends (MySQL, PostgreSQL) and cater to the different providers (Azure, AWS).