Skip to content

Releases: uselagoon/lagoon

lagoon-core v2.15.3

24 Jul 00:48
@tobybellwood tobybellwood
v2.15.3
c301efa
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
lagoon-core v2.15.3

Notes on this release

This release brings in a number of backend changes - a few code rewrites, tidyups and performance improvements. There are also fixes in place to allow the sharing of S3 buckets for backups, and better supporting cancelling tasks.

Additionally the test process has been updated to use Kubernetes 1.26 as a default, and the release process now creates multiarchitecture images, allowing lagoon-core to run on ARM-based processors (with the exception of the SSH service).

The version of Keycloak used for Lagoon has been upgraded to 17.0.1. In order to upgrade further than this, a rewrite of a number of elements in the lagoon keycloak initialisation will be required to support Quarkus.

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

What's Changed

Linked releases:

Full Changelog: v2.15.2...v2.15.3

Contributors

timclifford, tobybellwood, and 2 other contributors
Assets 2
Loading

lagoon-core v2.15.2

04 Jul 07:27
@tobybellwood tobybellwood
v2.15.2
0955bf9
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
lagoon-core v2.15.2

Notes on this release

This is a security release - addressing GHSA-75pm-pmwq-gg2c

This is also a patch release, fixing some minor bugs, and introducing some new queries

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

What's Changed

Linked releases:

Full Changelog: v2.15.1...v2.15.2

Contributors

tobybellwood, shreddedbacon, and CGoodwin90
Assets 2
Loading

lagoon-core v2.15.1

13 Jun 09:49
@tobybellwood tobybellwood
v2.15.1
1026e45
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
lagoon-core v2.15.1

Notes on this release

This is a patch release, fixing some minor bugs, and introducing no new features.

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

What's Changed

Linked releases:

Full Changelog: v2.15.0...v2.15.1

Contributors

bomoko, AlannaBurke, and 3 other contributors
Assets 2
Loading

lagoon-core v2.15.0

13 May 03:10
@tobybellwood tobybellwood
v2.15.0
8447e98
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
lagoon-core v2.15.0

Notes on this release

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

There are a number of small improvements in this release that will help to improve the ability to manage a Lagon instance:

  • Two new queries - allUsers and userByEmail - to better manage users, and one EnvironmentsByKubernetes to better understand what workloads are running on which cluster
  • The ability to specify a particular build image to use on any given projects - better enabling issue diagnosis and test-ahead.
  • Platform Owners now have the ability to use more previously admin-only queries, reducing the need for admin tokens
  • A couple of updates to streamline the calling and operation of subscriptions in the UI
  • quite a few tidyups in the operation of tasks and their related permissions.
  • (and the related release of the UI contains a "dark mode" 🥳 )

What's Changed

New Contributors

Linked releases:

Full Changelog: v2.14.2...v2.15.0

Contributors

rocketeerbkw, bomoko, and 3 other contributors
Assets 2
Loading

lagoon-core v2.14.2

11 Apr 22:32
@tobybellwood tobybellwood
v2.14.2
1908bda
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
lagoon-core v2.14.2

Notes on this release

This release fixes a bug found in the Keycloak optimizations under extreme load and re-enables the Redis functionality disabled in #3397 - this release should be used in place of v2.14.1

Please note, there was no lagoon-core 2.14.0 release, this is the second release in the 2.14 range. (2.14.0 was tag-only)

This release was built on https://github.com/uselagoon/lagoon-images/releases/tag/23.3.0 images

What's Changed

Linked releases:

Full Changelog: v2.13.0...v2.14.2

Contributors

rocketeerbkw, AlannaBurke, and 3 other contributors
Assets 2
Loading

[SUPERSEDED] lagoon-core v2.14.1

30 Mar 02:54
@tobybellwood tobybellwood
v2.14.1
c5708ed
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
[SUPERSEDED] lagoon-core v2.14.1

Notes on this release

You should use https://github.com/uselagoon/lagoon/releases/tag/v2.14.2 in place of this release. If you have already installed it, you should look to upgrade, however, the issue discovered is only present in extreme load scenarios.

Please note, there was no lagoon-core 2.14.0 release, this is the first release in the 2.14 range. (2.14.0 was tag-only)

Linked releases:

Full Changelog: v2.13.0...v2.14.1

Assets 2
Loading

lagoon-core v2.13.0

08 Mar 05:36
@tobybellwood tobybellwood
v2.13.0
6632815
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
lagoon-core v2.13.0

What's Changed

Linked releases:
lagoon-ui: https://github.com/uselagoon/lagoon-ui/releases/tag/core-v2.13.0
lagoon-build-deploy: https://github.com/uselagoon/build-deploy-tool/releases/tag/core-v2.13.0
lagoon-charts:
lagoon-core: https://github.com/uselagoon/lagoon-charts/releases/tag/lagoon-core-1.25.0
lagoon-test: https://github.com/uselagoon/lagoon-charts/releases/tag/lagoon-test-0.43.0

Full Changelog: v2.12.0...v2.13.0

Contributors

rocketeerbkw, bomoko, and shreddedbacon
Assets 2
Loading

lagoon-core v2.12.0

04 Feb 06:39
@tobybellwood tobybellwood
v2.12.0
f7a513b
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
lagoon-core v2.12.0

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

There are a number of changes in here - a lot to documentation, improved testing, and local development workflow - we've done a lot of work on improving the documentation, modernizing, and consolidating tests.

We've also updated all Alpine-based images to 3.17, RabbitMQ to 3.10, and the MariaDB version used for the api-db and keycloak-db.

There are a number of improvements to the API - bug fixes, adding additional logic, and handling some new functionality in other services.

Errata and observed issues

The update to the MariaDB version has caused a change in the way that metadata fields are returned from the API. Data is now returned as structured JSON, instead of an escaped string:

Now returning

metadata": {
				"key": "value"
			},

instead of previously
"metadata": "{\"key\": \"value\"}",

Any customers using the returned metadata field programmatically should make suitable accommodations in their tooling.

Important: Ensure you have a local backup of the api-db and keycloak-db before you commence this update

The update of these databases from MariaDB 10.4 to 10.6 should update seamlessly. In the event it does not go smoothly, the image cannot be rolled back owing to incompatible storage engines. You will need to drop the db and restore the backup to get running again.

Associated releases

The lagoon-ui version released with this lagoon-core release is https://github.com/uselagoon/lagoon-ui/releases/tag/core-v2.12.0
The build-deploy-tool version released with this lagoon-core release is https://github.com/uselagoon/build-deploy-tool/releases/tag/core-v2.12.0
The lagoon-charts version for this lagoon-cire release is https://github.com/uselagoon/lagoon-charts/releases/edit/lagoon-core-1.23.0
There are a number of other Lagoon-charts releases concurrent with this release, and they have made Kubernetes 1.21 the minimum supported version for Lagoon v.2.12.0 onwards.

What's Changed - Services

What's Changed - Documentation, Testing and Local Development

Full Changelog: v2.11.0...v2.12.0

Contributors

rocketeerbkw, dasrecht, and 6 other contributors
Assets 2
Loading

lagoon-core v2.11.0

27 Nov 21:19
@tobybellwood tobybellwood
v2.11.0
d248df5
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
lagoon-core v2.11.0

What's new

There are a couple of major changes hidden in this release:

  • The controller-handler functionality has been integrated into the actions handler (one more service consolidated 🥳) - there will be no outwards facing changes because of this, just more streamlining
  • The storage-calculator service in lagoon-core has been deprecated in favor of one located in lagoon-remote, to enable better control over when/where the storage runs are processed
  • A new migrations capability has been introduced to Lagoon - we are using knex to handle our migrations in a separate service, allowing us more flexibility with the api-db in the future (watch this space)
  • Migration of Keycloak startup scripts - note that this may take a few minutes to startup - this is normal, even if the liveness/startup probes fail - we're working on it - it has completed once the Config of Keycloak done. Log in via admin user 'admin' and password message comes up.
  • Added new addOrUpdateEnvVariableByName, getEnvVariablesByProjectEnvironmentName and deleteEnvVariableByName resolvers to allow in-place updating of Lagoon variables.
  • We've updated the permissions in Lagoon to only allow administrators to rename projects, as the knock-on ramifications to other systems (logging, backups, monitoring) could be serious if a user renames a project themselves.
  • A few assorted upgrades - RabbitMQ to 3.9, Alpine 3.16 in some images,
  • Removing some of the log verbosity in the core services (and being able to control it with a variable)
  • Tidy-ups to a few services to remove some errors, and build reporting/status inconsistencies.
  • This release is built using https://github.com/uselagoon/lagoon-images/releases/tag/22.11.0

Lagoon Builds

This release also incorporates https://github.com/uselagoon/build-deploy-tool/releases/tag/core-v2.11.0, which brings:

  • Configurable support for deploying workloads on spot instances
  • Support for buildkit features in builds (--target in docker-compose, and specifying DOCKER_BUILDKIT)
  • Adding Opensearch as a lagoon.type
  • A few other tidyups

Lagoon UI

This release also incorporates https://github.com/uselagoon/lagoon-ui/releases/tag/core-v2.11.0, which brings:

  • Raw Logs display option button
  • Ability to add plugins to the UI (eg the amazee.io supportBot)

Lagoon Charts

The chart releases to match the deprecated/consolidated/added services are in https://github.com/uselagoon/lagoon-charts/releases/tag/lagoon-core-1.16.0

What's Changed

New Contributors

Full Changelog: v2.10.0...v2.11.0

Contributors

rocketeerbkw, bomoko, and 7 other contributors
Assets 2
Loading

lagoon-core v2.10.0

07 Oct 06:47
@tobybellwood tobybellwood
v2.10.0
42f754e
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
lagoon-core v2.10.0

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

Contributors

achton, bomoko, and 8 other contributors
Assets 2
Loading