Lagoon v2.21 released

We are excited to announce the release of Lagoon v2.21.

What’s New in v2.21?

This release includes a series of new features and enhancements to improve user flexibility and security.

Deprecating Unsupported and Unmaintained Images

Unsupported or unmaintained images may have unresolved vulnerabilities, creating security risks for customers. Deprecation ensures users migrate to more secure, maintained versions.

There are now warnings in the Lagoon UI and Docker Desktop. We will continue to post the warning and while at this time we do not intend to remove out-of-date images, we could potentially block builds in the future.

Lagoon users take heed: we cannot guarantee compatibility with potentially broken builds forever. It is in your best interest to keep your code up to date, and action any build warnings that Lagoon detects.

Warnings can be viewed in Docker Desktop, via a docker inspect command or in future releases of Lagoon, highlighted in a build.
If the image has a suggested replacement, it will be mentioned in the warning.

Example:

To learn more please read further here in the Lagoon documentation.

Multiple Volume Mounts

By supporting multiple volume mounts per pod, a single pod can access multiple persistent storage locations, which is essential for enabling more applications, frameworks, and languages to run on Lagoon. This feature boosts Lagoon’s ability to run diverse and complex setups within a single pod architecture.

Path Based Routing

Path-based routing within an environment means that an ingress can direct traffic to different services based on the request’s URL path. This enhancement, which allows routing multiple paths to different services within the same ingress or namespace ultimately improves flexibility, scalability, and simplicity in how traffic is managed across multiple services in an environment.

Base Image Refresh

For projects that use custom upstream images, there is now additional functionality that forces Lagoon to check for a new image automatically on every build, just by adding the lagoon.base.image: label to any image in the docker-compose.yml file and setting the value to the upstream image you want to check.

Upgrade to Keycloak 24

This upgrade ensures better security, performance, and usability for managing identities and access. It will also give Lagoon greater support for authentication methods, and you can expect to hear more from us on this in the coming months.

Conclusion

Our latest release is a commitment to enhancing and improving Lagoon and the user experience. These updates are designed to help our customers manage their environments more effectively and securely.

Additionally, we are working with users to understand the importance of maintaining your code base and fixing errors. Together, we're building a more robust, efficient, and user-friendly platform that empowers your development process.