We’ve recently released our upgrade and deprecation policies, and wanted to spotlight them, along with a new home for our release notes in the documentation.
Releases
You can now find each release of Lagoon in the docs, in a new Releases section. The notes will include any important information, including deprecations and upgrades for that release.
Deprecations
Deprecations will continue to be announced in releases, and tracked in the release where the deprecation occurs. They’ll include a rough timeline (for example, we plan to deprecate X in 3 months or in the next release). You can find deprecations for each release in this section of the docs, along with our deprecation policy: https://docs.lagoon.sh/releases/policy/.
For example, looking at the release page for v2.17.0, we have the following deprecation info:
activestandby task image
This release introduces a new active/standby task image that does not require the use of the dioscuri controller. Dioscuri is deprecated and will eventually be removed from the lagoon-remote helm chart. If you use active/standby functionality in your clusters, you should upgrade to lagoon v2.17.0 and update your remote clusters to the version of the lagoon-remote helm chart the v2.17.0 release says to use (see release notes for v2.17.0)API Harbor support
Support for Harbor in the API will be removed in a future release. If you currently have your core installation with Harbor support, you should move to using the integration within lagoon-remote instead. See the documentation here and read the section about Harbor.Harbor 2.1 and earlier support
Support for Harbor 2.1.x (chart version 1.5.x) and older in lagoon-remote will be removed in a future release. You should consider upgrading Harbor to a newer version (currently Lagoon supports up to v2.9.x (chart version 1.13.x)), following any recommended upgrade paths from Harbor.
Upgrades
We have also published our upgrade policy, which you can view here: https://docs.lagoon.sh/releases/policy/. Each release page will also include any needed upgrades. For example, in v2.15.2, you can see the following upgrade on the release page:
This release was superseded, and the 2.15.4 release is recommended to be installed instead.
Our general policy is that you should upgrade to each minor version before you upgrade to the latest version.
You should check all upgrade requirements and deprecation notices for all versions as you upgrade.
An example of our suggested policy is as follows:
Currently installed v2.14.0, planning to upgrade to v2.17.0
Upgrade to v2.15.0
Upgrade to v2.16.0
Upgrade to v2.17.0
We hope this information is helpful in your management of Lagoon! Is there anything else you need to know? Hop in the Lagoon Discord and let us know!
And don’t forget our 2024 Community Survey! Tell us how the Lagoon community can best serve you.
Top comments (0)