nexus changelog¶
0.1.3¶
Released 2026-10-13.
Changes¶
Write chart labels as literals (#7)¶
Every chart built its labels through a helper that took a dict and
returned all five labels, so a reader had to open the helper to learn
what an object is called. app, app.kubernetes.io/name and
app.kubernetes.io/component are now literal lines on each object. One
helper per chart,
The nextcloud topology table is gone as well: the console keys (runtime, vcs-uri, connects-to, custom-icon) are literal lines on the workloads.
A value stays an expression where it must follow a name that is one: the fullname in mkdocs, omniroute and mailu, the upstream name override in mailu, and the loop and helper arguments in nextcloud.
No selector, pod template or value changes. The rendered objects are the same as before.
The contributor rules still asked for one helper that emits all five
labels. They now state what the charts do: three literal labels on
each object,
ci/check_labels.py reads the rendered objects, not the helper, so it needs no change.
The templates of every chart changed, and a change to a chart raises its version. The rendered objects are the same, so this is a patch.
nextcloud keeps bundling mailu 0.1.5: the dependency is resolved from the published repository, and 0.1.6 renders the same objects.
0.1.2¶
Released 2026-10-11.
Changes¶
Label every chart object¶
Every object a chart renders from its own templates now carries app and the app.kubernetes.io labels name, component, part-of and version, so the console and label queries can tell which application and which component an object belongs to. Each chart gets one small helper that emits them.
Workloads and the database and cache resources also get a runtime icon, the upstream source address and, where a component depends on another, a connects-to arrow for the topology view.
The labels sit on the object's own metadata only. Pod templates and selectors are unchanged, so an upgrade restarts no pod. Three charts hash a rendered file into a pod annotation (n8n, odoo, vaultwarden): that hash is taken without the new labels and keeps its value.
Objects of the upstream subcharts are labelled where the upstream chart has a value that reaches object metadata only: the workload of bifrost, the objects of mailu except its Redis subchart, and the workload, volumes and imaginary Service of nextcloud.
All ten charts move up one patch version.
0.1.1¶
Released 2026-10-07.
Changes¶
Name GRN.CLOUD B.V. as chart provider¶
0.1.0¶
Released 2026-10-05.
Changes¶
Add nexus chart¶
Nexus Repository from the upstream image: one Deployment, a data volume, Service and Route. No operator: the community operator the platform used needs a per-namespace install and pod fixes a tenant cannot apply. Runs under restricted-v2; the admin password is set at the first start from a Secret generated once.