This is the chart release corresponding to Lagoon release https://github.com/uselagoon/lagoon/releases/tag/v2.9.0
Note: Please ensure that there are no "Billing Groups" in your keycloak that are named the same as Lagoon groups, as this will cause issues with the Keycloak upgrade. More information to follow (or contact the Lagoon team via Slack/DIscord)
With the latest release of lagoon (v2.9.0) introducing a few changes to the build image, there may be some incompatibilities with previous releases of Lagoon.
For users who do not set the OVERRIDE_BUILD_DEPLOY_DIND_IMAGE variable (or it's values file equivalent overrideBuildDeployImage in lagoon-remote/lagoon-build-deploy) - you will always be using the kubectl-build-deploy-dind:latest image, which is pinned to the latest lagoon release (which will be ahead of the version currently installed on your Lagoon core).
We would strongly advise you to pin this image to the same version as your deployed Lagoon - the version id's are the same. (i.e use v2.8.4 for both lagoon-core and the override image).
Amazee.io has made a github action to pull and tag a specified image to a docker alias so that they can centrally control the version used in their clusters (they have a LOT of remotes to keep updated) - this allows them to easily roll forward/back the version as required - https://github.com/amazeeio/build-deploy-image-retagger - from Lagoon 2.10.0 the Lagoon team will likely be recommending people to do something similar for their specific version.