Merge pull request #3842 from uselagoon/docs/post-222

Update makefile and docs post 2.22 release

Jenkinsfile

@@ -230,7 +230,7 @@ pipeline {
         TOKEN = credentials('git-amazeeio-helmfile-ci-trigger')
       }
       steps {
-        sh script: "curl -X POST -F token=$TOKEN -F ref=lagoon_v222 https://git.amazeeio.cloud/api/v4/projects/86/trigger/pipeline", label: "Trigger lagoon-core helmfile sync on amazeeio-test6"
+        sh script: "curl -X POST -F token=$TOKEN -F ref=main https://git.amazeeio.cloud/api/v4/projects/86/trigger/pipeline", label: "Trigger lagoon-core helmfile sync on amazeeio-test6"
       }
     }
     stage ('push images to uselagoon/*') {

Makefile

@@ -413,7 +413,7 @@ STERN_VERSION = v2.6.1
 CHART_TESTING_VERSION = v3.11.0
 K3D_IMAGE = docker.io/rancher/k3s:v1.31.0-k3s1
 TESTS = [nginx,api,features-kubernetes,bulk-deployment,features-kubernetes-2,features-variables,active-standby-kubernetes,tasks,drush,python,gitlab,github,bitbucket,services,workflows]
-CHARTS_TREEISH = lagoon_v222
+CHARTS_TREEISH = main
 TASK_IMAGES = task-activestandby
 
 # the name of the docker network to create

docs/releases/2.22.0.md

@@ -2,16 +2,38 @@
 * lagoon [v2.22.0](https://github.com/uselagoon/lagoon/releases/tag/v2.22.0)
 * lagoon-ui [core-v2.22.0](https://github.com/uselagoon/lagoon-ui/releases/tag/core-v2.22.0)
 * lagoon-build-deploy [core-v2.22.0](https://github.com/uselagoon/build-deploy-tool/releases/tag/core-v2.22.0)
-* lagoon-core chart [x.xx.x](https://github.com/uselagoon/lagoon-charts/releases/tag/lagoon-core-x.xx.0)
-* lagoon-remote chart [x.xx.x](https://github.com/uselagoon/lagoon-charts/releases/tag/lagoon-remote-x.xx.x)
+* lagoon-core chart [1.49.0](https://github.com/uselagoon/lagoon-charts/releases/tag/lagoon-core-1.49.0)
+* lagoon-remote chart [0.95.0](https://github.com/uselagoon/lagoon-charts/releases/tag/lagoon-remote-0.95.x)
 
 ## Release Notes
 
-tbc - Not released yet
+This release is a standard Lagoon release. There are changes required for teams managing their own Lagoon installations (core and remote).
 
 ## Upgrades
 
-tbc
+Self-managed Lagoon installs will need to be aware of three changes in lagoon-core and lagoon-remote. Please read the following sections carefully to ensure you update components that apply to your installation correctly.
+
+### Lagoon Custom Resource Definitions (CRDs)
+
+We introduced a new API version of the Lagoon Build and Task CRDs in https://github.com/uselagoon/lagoon-charts/pull/688. You must upgrade these after installing the latest version of `lagoon-remote`. Failure to update the CRDs will result in the remote controller failing to start, or builds and tasks failing.
+
+If you're installing the version defined in the top of these release notes, you can use the following to upgrade the CRDs to the version required.
+
+```
+helm show crds lagoon/lagoon-build-deploy --version 0.30.2 | kubectl apply -f -
+```
+
+Alternatively, see the [README in the lagoon-build-deploy chart](https://github.com/uselagoon/lagoon-charts/blob/main/charts/lagoon-build-deploy/README.md#lagoon-remote) for further examples on how to update the Lagoon Build and Task CRDs.
+
+### DockerHost StatefulSet
+
+To help with improving or distributing build loads, we converted the docker-host from a `Deployment` to a `StatefulSet` in https://github.com/uselagoon/lagoon-charts/pull/687. This allows the docker-host to be scaled.
+
+This will provide the ability to load-balance docker build workloads. It will result in a new docker-host cache being created the first time any replica starts up (including on the first deployment), this may result in the first few builds being less-optimized whilst the cache rebuilds. This StatefulSet must only be scaled up or down via helm, and not directly in kubernetes otherwise the load-balancing of the workloads will not be able to be fully utilised.
+
+### NATS / SSH Portal
+
+The version of NATS used by Lagoon was updated in https://github.com/uselagoon/lagoon-charts/pull/602. If your installation of Lagoon utilises SSH portals and NATS, you need to be aware of changes to the structure of the NATS values. This upgrade requires minimal config structure changes in your lagoon-core and lagoon-remote values files. There are no changes to the certs or keys, just the naming of the YAML items. See the pullrequest description for more information.
 
 ## Deprecations