Skip to content

Releases: uselagoon/lagoon

v1.7.0 #BlackLivesMatter

23 Jun 01:14
@github-actions github-actions
v1.7.0
670efb4
Compare
Choose a tag to compare
v1.7.0 #BlackLivesMatter

⠀⠀⠀⠀⠀⠀⠀⠀⣴⣶⣿⣿⣿⣿⣿⣿⣶⣦⣤⣀⠀⠀⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⣠⣴⣿⣿⠿⠛⠉⢉⣿⣄⠀⠉⠉⠉⠛⠿⣿⣿⣦⣄⠀⠀⠀⠀⠀
⠀⠀⠀⣠⣾⣿⠿⠉⠀⠀⠀⣰⣿⣿⣿⢃⣶⡀⠀⠀⠀⠀⠙⢿⣿⣷⣄⠀⠀⠀
⠀⠀⣴⣿⡟⠃⠀⠀⠀⣰⣶⣮⣝⡻⢡⣿⣿⣿⡆⣀⠀⠀⠀⠀⠙⢿⣿⣦⠀⠀
⠀⣼⣿⡟⠀⠀⠀⢀⣼⣿⣿⣿⣿⣿⣷⣮⠹⢋⣾⣿⣷⡄⡀⠀⠀⠀⢻⣿⣧⠀
⢰⣿⡟⠀⠀⠀⢠⣾⣿⣿⡿⠎⣛⣿⣿⡟⣰⣿⣿⡿⢋⣼⣷⡀⠀⠀⠀⢻⣿⡆
⣿⣿⡇⠀⠀⠀⠻⣿⣿⣿⣿⣷⣦⠨⣭⣘⡿⣿⢟⣵⣿⣿⠿⠋⠀⠀⠀⢸⣿⣿
⣿⣿⠀⠀⠀⠀⠀⠙⣿⣿⣿⣿⣿⣷⡘⣿⣿⣷⣝⢿⣿⣵⡇⠀⠀⠀⠀⠀⣿⣿
⣿⣿⡇⠀⠀⠀⠀⠀⠘⢿⣿⣿⣿⣿⣿⡌⢿⣿⣿⣿⣿⣿⠁⠀⠀⠀⠀⢸⣿⣿
⠸⣿⣧⠀⠀⠀⠀⠀⠀⠈⠻⣿⣿⣿⣿⣿⠎⢿⣿⣿⣿⠏⠀⠀⠀⠀⠀⣼⣿⠇
⠀⢻⣿⣧⠀⠀⠀⠀⠀⠀⠀⣹⣿⣿⣿⣿⡆⣾⣿⣿⠃⠀⠀⠀⠀⠀⣼⣿⡟⠀
⠀⠀⠻⣿⣧⡄⠀⠀⠀⠀⠀⣿⣿⣿⣿⣿⢃⣿⣿⣿⠀⠀⠀⠀⣠⣼⣿⠟⠀⠀
⠀⠀⠀⠙⢿⣿⣶⣀⠀⠀⢠⣿⣿⣿⣿⣿⢸⣿⣿⣿⠀⠀⣀⣾⣿⡿⠋⠀⠀⠀
⠀⠀⠀⠀⠀⠙⠻⣿⣿⣶⣼⣿⣿⣿⣿⣿⣸⣿⣿⣿⣶⣿⣿⠟.

#BlackLivesMatter

Changes in this release

API & Authentication subsystem

Admin & User Interfaces subsystem

Build & Deploy subsystem

Logging & Reporting subsystem

  • Logging overhaul @smlx (#1959)
  • Make lagoon-logging helm chart OpenShift compatible @smlx (#1918)
  • Add missing builddeploy-kubernetes:complete task to RC notifications @twardnw (#1973)
  • Improve resilience of logs-forwarder @smlx (#1940)

Base Images & Testing subsystem

Documentation & Examples / DX subsystem

Automation, Services & Helpers subsystem

Security subsystem

Assets 2
Loading

Welcome Drupal 9! - v1.6.0

02 Jun 00:28
@github-actions github-actions
v1.6.0
0483426
Compare
Choose a tag to compare
Welcome Drupal 9! - v1.6.0

Drupal 9 support, Lagoon metadata and Trivy scanning

  • The main reason for this release is to ensure that our images and infrastructure are ready to support Drupal 9 on release day. We’ll also be releasing a blog post outlining what we’ve put in place.
  • This release has also added customisable metadata fields to Lagoon projects, contributed by @stooit (and thanks to Salsa Digital) - we’ll expand more on what’s possible with this, and why it’s so important shortly.
  • Also, in big ticket items, we have updated the image and vulnerability scanning component bundled with our Harbor install to use Trivy (instead of Clair). In our tests, Trivy not only detected more vulnerabilities, but was significantly less resource-heavy, and returned faster results - triple win!

Update to v1.6.0

With #1917 landed within Lagoon v1.6.0 we're now labeling all new created OpenShift and Kubernetes Namespaces with two new Labels: lagoon.sh/project and lagoon.sh/environment.
In order to label all existing namespaces please use this script:

#!/usr/bin/env bash

while read PROJECT; do
  echo "Handling lagoon project ${PROJECT}"
  while read LINE; do
    NAMESPACE=$(echo "$LINE" | awk '{print $5}')
    ENVIRONMENT=$(echo "$LINE" | awk '{print $2}')
    if kubectl get ns ${NAMESPACE} &> /dev/null; then
      PATCH="{\"metadata\": {\"labels\": {\"lagoon.sh/project\": \"${PROJECT}\", \"lagoon.sh/environment\": \"${ENVIRONMENT}\"}}}"
      echo "Updating namespace labels for ${NAMESPACE}"
      kubectl patch ns "${NAMESPACE}" -p "${PATCH}"
    else
      echo "${NAMESPACE} not found on this cluster"
    fi
  done < <(lagoon list environments --no-header --project="${PROJECT}")
done < <(lagoon list projects --no-header | awk '{print $2}')

this requires lagoon-cli >=v0.9.1 and kubectl, both fully authenticated against Lagoon and an OpenShift/Kubernetes cluster, run the script for each cluster that is managed by Lagoon.

Changes in this release

API & Authentication subsystem

  • Re-implement JWT generation script using pyjwt @smlx (#1830)
  • Added support to arbitrary project metadata key/value pairs @stooit (#1775)

Admin & User Interfaces subsystem

Build & Deploy subsystem

Logging & Reporting subsystem

Base Images & Testing subsystem

Documentation & Examples / DX subsystem

Automation, Services & Helpers subsystem

Security subsystem

  • Re-implement JWT generation script using pyjwt @smlx (#1830)

Release side notes

Assets 2
Loading

v1.5.0 - And we thought this is just gonna be a small one

10 May 15:07
@github-actions github-actions
v1.5.0
9867056
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
v1.5.0 - And we thought this is just gonna be a small one

The name of this release says it all: Originally v1.5.0 was expected to have a couple of fixes while we're working on v2.0.0 of Lagoon. But then the Lagoon Gods had something different in mind:

Our security A-12 @smlx found another security issue (on a Friday evening in Australia nonetheless) and so the US team (it being only Friday morning at that time) joined forces. Security bug slayer @cdchris12 with support of rollout strategy consultant @twardnw and pull request review hawk @Schnitzel got a PR formed that used as much as automated update magic as possible, in order to create the least amount of work for any Lagoon Maintainer Magicians out there.
After a couple of hours the PR finally passed (e38818c) and was ready to set sail. As this is a security release, we hot-released fixed images on all Lagoon versions managed by the Lagoon Maintainer Squadron and of course found another bug that was promptly fixed (#1861) and confirmed by master tester @shreddedbacon. While in the same time PR and Issue organizer @tobybellwood made sure that the Lagoon milestones were aligned to the new world order.

Just a couple of hours after the security bug was discovered, the Lagoons are safe again and this release marks the second security release of Lagoon.

Upgrade Instructions

During the release of 1.5.0 (not waiting until the build pod has finished!)

  1. Immediately after keycloak-db has restarted, run: 
    mysql -e "SET PASSWORD FOR '$MARIADB_USER'@'%' = PASSWORD('$MARIADB_PASSWORD'); FLUSH PRIVILEGES;"
    inside the keycloak-db pod.
  2. Immediately after keycloak-db has restarted, run: 
    /rerun_initdb.sh
    inside the api-db pod.

Failure to do these two things might cause the api and keycloak pods to not be able to connect to the databases and cause a downtime of Lagoon and a failed build.
To recover: run the two commands in the respective db pods and trigger another Lagoon build.

API & Authentication subsystem

Admin & User Interfaces subsystem

Build & Deploy subsystem

Logging & Reporting subsystem

Base Images & Testing subsystem

Documentation & Examples / DX subsystem

  • Added documentation snippet for generating JWT on command line. @nicksantamaria (#1796)
  • Add Github issue template config with a link to Discussions feature @dan2k3k4 (#1821)
Assets 2
Loading

v_______1_______._______4_______._______1

09 Apr 17:04
@github-actions github-actions
v1.4.1
6ff4db7
Compare
Choose a tag to compare
v_______1_______._______4_______._______1

Changes in this release

API & Authentication subsystem

Build & Deploy subsystem

Logging & Reporting subsystem

  • Fix issue with elasticsearch buffers overflowing in logs-forwarder @smlx (#1738)

Base Images & Testing subsystem

Documentation & Examples / DX subsystem

Automation, Services & Helpers subsystem

Security subsystem

Alternative Release Names

  • Quarantine Edition
  • social distancing edition
  • Flaming Poisoning Raging Sword Of Doom
  • "The One-Four-One"
  • v1.4.1 - six feet / two meters distance
Assets 2
Loading

v1.4.0 - Lagoobernetes

01 Apr 23:04
@github-actions github-actions
v1.4.0
b82dfaf
Compare
Choose a tag to compare
v1.4.0 - Lagoobernetes

This release marks the first version of Lagoon with support to deploy into Kubernetes. It is though in no way suggested to use this for Kubernetes deployments yet, not every feature of Lagoon is supported and there is no full documentation yet. This will follow with Lagoon 2.0.0 following in the next weeks.

It is though a big step for Lagoon and saying that we are super excited is an understatement. Thanks everybody for their tremendous amount of work.

Changes in this release

Vanilla Kubernetes support

API & Authentication subsystem

Build & Deploy subsystem

Logging & Reporting subsystem

Operators & Provisioning subsystem

Base Images & Testing subsystem

Documentation & Examples / DX subsystem

Automation, Services & Helpers subsystem

Assets 2
Loading

v1.3.1 - Friday the 13th

13 Mar 19:17
@Schnitzel Schnitzel
v1.3.1
b9c0ac6
Compare
Choose a tag to compare
v1.3.1 - Friday the 13th

This is a hotfix release for the issues we found in #1722

Changes in this release

API & Authentication subsystem

Logging & Reporting subsystem

Assets 2
Loading

v1.3.0 - The One Without PHP 5.6

12 Mar 03:41
@github-actions github-actions
v1.3.0
28f9005
Compare
Choose a tag to compare
v1.3.0 - The One Without PHP 5.6

More information over at https://stories.amazee.io/what-to-expect-in-lagoon-1-3-0-6683bc19e8c8

Headline Items

  • Incorporating the security release v1.2.1
  • Self-service SSH key updating in the UI
  • Much better timeframe-based Cronjob allocation
  • Image deprecations for PHP 5.6, 7.0 and 7.1, NodeJS 6, 8 and 9
  • Upstream alpine and minor version image pinning for predictability
  • Release (and incorporation) of the brand new amazee.io database-as-a-service operator
  • Billing automation
  • Documentation super-overhaul

API & Authentication subsystem

Build & Deploy subsystem

Logging & Reporting subsystem

Operators & Provisioning subsystem

Base Images & Testing subsystem

Documentation & Examples / DX subsystem

Automation, Services & Helpers subsystem

Security subsystem

  • Updating default HAProxy config to conform to current industry standards @cdchris12 (#1551)
Assets 2
Loading

1.21 gigawatts? Great Scott! (v1.2.1)

08 Feb 05:52
@Schnitzel Schnitzel
v1.2.1
c1b2484
Compare
Choose a tag to compare
1.21 gigawatts? Great Scott! (v1.2.1)

This is a security release of Lagoon! Learn more at #1646 about the vulnerability

As this is a security release that has already been applied to production clusters, and v1.3.0 is due out in the next week, no base images have been published to docker hub for this release.

Full list of changes by subsystem

API & Authentication:

Build & Deploy:

Testing and Local Development:

Release Video:

https://www.youtube.com/watch?v=I5cYgRnfFDA

Alternative Release Names:

  • MultiPass
  • These are not the tokens you’re looking for
  • Just When You Thought We Couldn’t Get Any More Parallel Branches, We Go And Pull A Stunt Like This
  • The one where we discovered a vulnerability, patched and released in 24 hours, all on a Friday
Assets 2
Loading

Hyperdodecahedron (v1.2.0)

17 Dec 16:16
@Schnitzel Schnitzel
v1.2.0
7cc2bb4
Compare
Choose a tag to compare
Hyperdodecahedron (v1.2.0)

More information over at https://stories.amazee.io/what-to-expect-in-lagoon-1-2-0-e62d9b3cc51a

Headline items:

  • First release of Harbor integration to Lagoon
  • More notification options (Microsoft Teams and e-mail)
  • Improved API and authentication performance
  • First release of amazee.io docker images for PHP 7.4
  • Last release of amazee.io docker images for PHP 5.6, 7.0 and 7.1

Full list of changes by subsystem

API & Authentication:

Build & Deploy:

Logging & Reporting:

Operators & Provisioning:

  • Add DB_READREPLICA_HOSTS to lagoon-env #1342 (@smlx)

Images:

Testing and Local Development:

Read more
Assets 2
Loading

🚒 🚑 🚓 (v1.1.2)

10 Oct 03:43
@Schnitzel Schnitzel
v1.1.2
877e264
Compare
Choose a tag to compare
🚒 🚑 🚓 (v1.1.2)

Another short fix. Sorry for any failed builds this might have caused.
PSA: Please do not use this version in an emergency, instead call 112.

Changes:

  • Stop using edge package versions for node and friends - the versions of node coming in alpine 3.10 are the same major versions as in edge now #1288
Assets 2
Loading