Skip to content

Releases: uselagoon/lagoon

lagoon-core v2.10.0

07 Oct 06:47
42f754e
Compare
Choose a tag to compare

Lagoon 2.10 - so many changes!!!

lagoon-charts

Lagoon operators should check the lagoon-charts release notes carefully, as there may be action needed - especially if you use custom image references for the docker-host, drush-alias, overrideBuildDeployImage or UI images

Service consolidation

A large number of services have either been consolidated, removed or transferred to new repositories - this is aiming towards Lagoon having a leaner, meaner core, and having more predictable release cycles for the various components.

  • kubectl-build-deploy-dind has now been consolidated and transferred to https://www.github.com/uselagoon/build-deploy-tool, and the deprecated kubectl, oc and oc-build-deploy-dind images now no longer built
  • lagoon-ui has now been transferred to https://www.github.com/uselagoon/lagoon-ui and adapted for more rapid build cycles (and easier contribution)
  • a host of service images (docker-host, drush-alias, athenapdf, logs-concentrator, logs-dispatcher) have now been transferred to https://www.github.com/uselagoon/lagoon-service-images as they no longer depend on lagoon-core, and can be independently updated
  • the individual logs2x services (slack, teams, rocketchat, email, webhooks, s3) have all been consolidated into a single logs2notifications service, that operates identically to the previous services.
  • Lagoon can now support running the storage-calculator in lagoon-remote as well as lagoon-core. This will be made available shortly at https://github.com/uselagoon/storage-calculator and added as an option to lagoon-remote in a future release.

Database updates

A large focus of this release is to prepare for a larger database upgrade in 2.11 - namely migrating from the MariaDB 10.4 pod, to a newer version of mariadb, with the added option of using a managed database service, such as RDS etc

  • All foreign keys have been removed from the api-db - they were non-functional anyway (and a couple were misconfigured). We will reassess whether we should use any foreign keys in future. This will be the final migration written to operate in api-db via raw SQL. As of 2.11, we will utilise an init process to trigger knex-based migrations.

Service updates

  • The golang based services have all been updated to Golang 1.18 and rejigged to share a common structure
  • The storage-calculator has been updated to a more recent version of kubectl and given improved error handling abilities

API updates

  • The ability to disable harbor-core integration (to be depracated in favor of harbor-remote) and opensearch integration (for installs not using lagoon-logs) has been added to the API as feature flags.
  • Specifying the lagoon-build-image to be used for a lagoon-remote has now been added to the API, along with sensible defaults to match the current release - this will avoid mismatches between lagoon-core and lagoon-remote releases, and place more control in the hands of Lagoon administrators. We will also shortly start work on compatibility checking between core and remote.
  • Environment and Project cleanup has been improved, with the API not allowing a project to be deleted if environments exist, and the removal of a project or environment triggering the removal of any associated variables from the API.
  • GraphQL support for a couple of new features in the UI - being able to filter deployments, and being able to request Lagoon Insights files from S3.
  • Additional fixes to Active/Standby, build variable merging, DeployTarget config and reading S3 buckets on S3-compatible hosts.
  • Audit logging now goes to a single consolidated index.

Local development and Test changes

  • The local development docker-compose has been updated to remove or repoint the consolidated/removed/transferred services
  • Some test routines have been reorganised to closer align durations to avoid potential issues in github actions

What's Changed

New Contributors

Full Changelog: v2.9.2...v2.10.0

lagoon-core v2.9.2

17 Aug 23:23
934f058
Compare
Choose a tag to compare

Updated in this release

This is a patch release of lagoon-core, addressing two main issues:

  • Adding a feature flag to non-default backup configurations (different prod and env retentions or schedules) - as this WILL have unintended consequences with the current compatible version of k8up
  • Minor fixes to the creation of autogenerated routes and the length of ingress labels.

The version of the build-deploy-tool used in this release is v0.15.2

What's Changed

Full Changelog: v2.9.1...v2.9.2

lagoon-core v2.9.1

01 Aug 21:25
be9ae85
Compare
Choose a tag to compare

This release updates the build-deploy-tool to v0.13.6 - bringing with it some improvements to routes and tasks.

What's Changed

New Contributors

Full Changelog: v2.9.0...v2.9.1

lagoon-core v2.9.0

15 Jul 09:12
fe4157a
Compare
Choose a tag to compare

Major changes this release:

  • Keycloak 16 upgrade - The keycloak-db has now been upgraded to v16 of Keycloak - this brings some great performance improvements, as well as some extra security enhancements
  • Implementation of build-deploy-tool for ingress and route tasks - initially released in v2.8.0, this has been refined to better handle edge cases. In builds where the docker-compose file is not valid or readable, the build will fail with the error message that requires fixing
  • Implementation of build-deploy-tool for conditional pre/post rollout tasks - as well as migrating the code for pre & post rollout tasks to the new build-deploy-tool, these tasks now support conditional definitions
  • Numerous documentation changes - now bigger and better than ever
  • Lagoon now builds and tests Kubernetes 1.23 in ci, in preparation for the next set of upgrades for 1.24

What's Changed

New Contributors

Full Changelog: v2.8.0...v2.9.0

lagoon-core v2.8.4

21 Jun 01:38
Compare
Choose a tag to compare

This patch release of Lagoon fully reverts the changes introduced in #3133 and #3141

The Lagoon team comprehensively tested these changes prior to release. However, on release, it became apparent that a very small minority of users were using docker-compose.yml files that were incorrectly formatted, and would therefore not be able to be effectively read using our automated tools.

These errors range from full syntax errors (that would prevent docker-compose from working) to minor issues that would cause it to work with some limitations, to other use cases not envisioned in developing our features.

In order to provide the best possible Lagoon experience, this release reverts the new functionality and instead introduces a docker-compose validate step that will raise an issue in the build logs if Lagoon discovers one of these errors. We still intend to release the updated build deploy code in Lagoon v2.9.0 but intend to monitor builds in the meantime to ensure that we've captured a wide range of configurations

tags v2.8.2 and v.2.8.3 have not been converted into releases and can be safely skipped.

Full Changelog: v2.8.1...v2.8.4

lagoon-core v2.8.1

09 Jun 09:05
Compare
Choose a tag to compare

This release is a hotfix release to remedy the issue raised in #3179, and a specific use case experienced when a user is a member of multiple projects. It has backported three PRs that will be released in Lagoon v2.9.0

If you are not utilising the LAGOON_BACKUP_DEV_RETENTION and LAGOON_BACKUP_PR_RETENTION variables to set alternate retention periods for development environments, you can skip this release and wait for v2.9.0 (released in the next day or so after this)

Changes in this release

Full Changelog: v2.8.0...v2.8.1

lagoon-core v2.8.0

18 May 09:00
1053965
Compare
Choose a tag to compare

In this release

This release contains a security fix for an opendistro index creation permission issue (see GHSA-7jj3-wwp7-989p)

This release also introduces a new set of logic for the build-deploy image, processing routes and ingresses via the new https://github.com/uselagoon/build-deploy-tool - gradually more of the logic will transfer across - see uselagoon/build-deploy-tool#27 for details

Additionally, the permissions needed to add environment variables to projects have been revised to match the use case, and can now be actioned by a user with "maintainer" permission, instead of the previous "owner".

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

The lagoon-charts update will follow shortly.

What's Changed

Full Changelog: v2.7.1...v2.8.0

lagoon-core v2.7.1

03 May 07:06
91a2531
Compare
Choose a tag to compare

This is a patch release to remedy a couple of issues found since releasing 2.7.0

What's Changed

Full Changelog: v2.7.0...v2.7.1

lagoon-core v2.7.0

26 Apr 09:46
a604be4
Compare
Choose a tag to compare

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

There are two feature updates in this release:

  • Making tasks more like deployments - with similar progress stages for reporting and tracking
  • Configurable backup schedules for non-production environments, with the ability to differentiate between PR and branch deployments. More information on how to configure them is in #3087

This release also remediates two earlier issues with S3 restore checks from v2.6.0 and some incorrect database migrations logic that caused the migrations not to run correctly.

What's Changed

Full Changelog: v2.6.0...v2.7.0

lagoon-core v2.6.0

08 Apr 08:31
a74d4e5
Compare
Choose a tag to compare

Security FIx

This release of Lagoon patches a security vulnerability present in Lagoon v2.5.0 only. In this release, a service-api client was added to Keycloak without a secret being automatically generated. This client isn't in a release yet (it is pre-work for the SSH portal coming shortly). THis v2.6.0 releae resolves this by automatically creating or rotating a secret. The corresponding charts release also allows for the definition of a secret, although this isn't supported in our version of keycloak yet.
If you are unable to upgrade to v2.6.0 immediately, you can log in to Keycloak, go to the service-api client, and click "Regenerate secret".

What's Changed

New Contributors

Full Changelog: v2.5.0...v2.6.0