Lagoon Compatibility
Tested Versions
| Lagoon Version | lagoon-core chart | lagoon-remote chart | Notes |
|---|---|---|---|
| v2.31.0 | 1.60.0 | 0.104.1 | Tested (single-cluster and multi-cluster) |
| v2.30.0 | 1.59.0 | 0.103.0 | Tested; known Knex migrations locking bug (fixed in v2.31.0) |
| v2.28.0 | 1.56.0 | 0.96.0 | Tested |
| v2.24.1 | 1.52.0 | 0.90.0 | Tested |
The provider is tested against these specific chart versions. Intermediate patch releases are generally compatible; major chart version changes may introduce GraphQL API changes that require a provider update.
Feature-Specific Requirements
| Feature | Minimum Lagoon Version | Notes |
|---|---|---|
Route resources (Route, ProjectAutogeneratedRouteConfig, EnvironmentAutogeneratedRouteConfig) |
v2.29.0 | Requires featureApiRoutes enabled on the Lagoon Organization |
| All other resources | v2.24.1 | Core CRUD operations supported from the earliest tested version |
The
featureApiRoutesflag is being deprecated toward general availability in Lagoon v2.29.0+. If you are running v2.29.0 or later and route resources are unavailable, check thatfeatureApiRoutesis enabled for your organization in the Lagoon API.
Multi-Version API Compatibility
The provider automatically falls back to older GraphQL queries for Lagoon instances that do not support newer API fields. The following operations have version-aware fallbacks:
| Operation | Modern API (v2.28.0+) | Fallback (v2.24.x) |
|---|---|---|
| Get project by ID | projectById query |
allProjects + filter |
| Get deploy target by ID | kubernetesById query |
allKubernetes + filter |
| Add environment variable | addEnvVariable mutation |
Legacy addEnvVariable |
| Delete environment variable | deleteEnvVariable mutation |
Legacy deleteEnvVariable |
| List advanced tasks | advancedTasksForEnvironment |
advancedTasksByEnvironment |
Known Issues by Version
Lagoon v2.30.0 — Knex migration locking bug
Lagoon v2.30.0 introduced a Knex database migration locking issue that causes the API to hang on startup if a previous migration was interrupted. The provider will time out on connection if this occurs. Upgrade to v2.31.0 to resolve it.
Lagoon v2.28.0 — CRD version detection
For Lagoon v2.28.0 (chart < 1.58.0), the provider uses v1beta1 as the CRD storage version for deploy target configs. For v2.29.0+ (chart >= 1.58.0), it uses v1beta2. Both versions are always served.
Provider Version History
See the Release Notes page for a full changelog, or the RELEASE_NOTES.md file on GitHub.