github uselagoon/lagoon v2.1.0
lagoon-core v2.1.0

latest releases: v2.21.0, v2.20.1, v2.20.0...
3 years ago

This release is built on the https://github.com/uselagoon/lagoon-images/releases/tag/21.9.0 images

Create new variable for project seed by @shreddedbacon in #2859

The Lagoon team identified a situation that may arise when a jwtsecret is rotated (following good security practice). The jwtsecret was used to create a password for the k8up repository, but also used to generate that password on each run. Changing the jwtsecret changes the password, so instead we have provided a projectseed instead, that doesn't need rotating, and is therefore safer to use to create these passwords reliably. We have added backward compatibility shims both in Lagoon and in the charts used to deploy Lagoon-core that will create this projectseed from the existing jwtsecret to ensure backwards compatibility

Experimental Support for multiple deployment targets per project by @shreddedbacon in #2829

Some of this functionality is in an early release phase, and all API schema calls are marked accordingly. The primary impact is that the storage of the DeployTarget (Kubernetes cluster) is now stored against the individual environment, as opposed to the project. This allows admins to configure a set of rules that determine which environments in a project deploy to specific clusters. Once an environment is allocated a DeployTarget, that is where that environment will always deploy. To manage the implementation of this, a procedure has been added to the api-db to ensure that all environments have the correct current DeployTarget added to them.

Please ensure you run the rerun_initdb.sh script after update to update all the projects for this change.

Improvements to build and task log stability by @shreddedbacon in #2862

In this release, a new service has been added to retrieve build and task logs from the lagoon-logs exchange and upload them to the S3 files bucket (along with task uploads). The API (and the UI) then retrieve these logs from that bucket instead of Elasticsearch. The logs are still currently configured to upload to Elasticsearch as well as S3. Additionally, a minio service is configured to hold the logs in local development.

Removing defaultMeta from all user activity logs by @timclifford in #2856

We picked up a situation where the user performing an action could occasionally be attributed to future actions in the audit logs. Making the user logging action more thread-safe fixes this, and removes the erroneous replication.

add X-Robots-Tag noindex, nofollow server-snippet to all ingresses by @tobybellwood in #2867

Previously all robots control was performed in the nginx base image. This PR has brought this forward into the creation of all the auto-generated ingresses (for all service types, not just nginx). This means that development environments, and production internal URLs are all covered automatically. There is a note in the documentation about use of additional server-snippets in .lagoon.yml.

What's Changed

New Contributors

Full Changelog: v2.0.0...v2.1.0

Don't miss a new lagoon release

NewReleases is sending notifications on new releases.