Platform users need to select particular versions of managed applications, such as tenant Kubernetes and databases.
Kubernetes
Current state (as of 2026-06)
The curated version enum pattern (a version values field backed by a files/versions.yaml major→image-tag map, validated at render time) is now established for 7 engines. The remaining managed apps are pinned to a single chart-baked version, and FoundationDB exposes an unvalidated free-form version.
| App |
Version selectable? |
Mechanism |
Versions offered |
| postgres |
Yes |
version enum → versions map |
v18, v17, v16, v15, v14, v13 (default v18) |
| mariadb |
Yes |
version enum → versions map |
v11.8, v11.4, v10.11, v10.6 (default v11.8) |
| mongodb |
Yes |
version enum → versions map |
v8, v7, v6 (default v8) |
| redis |
Yes |
version enum → versions map |
v8, v7 (default v8) |
| rabbitmq |
Yes |
version enum → versions map |
v4.2, v4.1, v4.0, v3.13 (default v4.2) |
| opensearch |
Yes |
version enum → versions map |
v3, v2, v1 (default v2) |
| kubernetes |
Yes |
version enum → versions map |
v1.35, v1.34, v1.33, v1.32, v1.31, v1.30 (default v1.35) |
| foundationdb |
Partial |
free-form cluster.version string (no enum/validation) |
default 7.3.63 |
| clickhouse |
No |
hardcoded in chart |
24.9.2 |
| harbor |
No |
hardcoded in chart |
2.14.2 |
| kafka |
No |
hardcoded in chart |
3.7.0 |
| nats |
No |
hardcoded in chart |
1.4.1 |
| openbao |
No |
hardcoded in chart |
2.5.0 |
| qdrant |
No |
hardcoded in chart |
v1.16.3 |
| http-cache |
No |
hardcoded (nginx) |
1.25.3 |
| tcp-balancer |
No |
hardcoded (haproxy) |
2.9.7 |
| vpn |
No |
hardcoded in chart |
1.8.1 |
| bucket / vm-disk / vm-instance / tenant / vpc |
N/A |
no engine-version concept |
— |
Gaps
- foundationdb:
cluster.version is a free-form string with no curated list or validation — should adopt the enum + files/versions.yaml pattern.
- High-value missing selection: clickhouse, kafka, harbor, openbao, qdrant are managed services pinned to one version; users cannot pick a major line and upgrades are coupled to Cozystack releases. clickhouse and kafka are the highest priority (data-tier major-version compatibility).
- Lower priority: http-cache, tcp-balancer, vpn, nats — single-version is more defensible for proxy/infra components.
Platform users need to select particular versions of managed applications, such as tenant Kubernetes and databases.
Kubernetes
Current state (as of 2026-06)
The curated
versionenum pattern (aversionvalues field backed by afiles/versions.yamlmajor→image-tag map, validated at render time) is now established for 7 engines. The remaining managed apps are pinned to a single chart-baked version, and FoundationDB exposes an unvalidated free-form version.versionenum → versions mapversionenum → versions mapversionenum → versions mapversionenum → versions mapversionenum → versions mapversionenum → versions mapversionenum → versions mapcluster.versionstring (no enum/validation)Gaps
cluster.versionis a free-form string with no curated list or validation — should adopt the enum +files/versions.yamlpattern.