mkdocs changelog¶
0.3.3¶
Released 2026-10-25.
Changes¶
Extra labels and annotations on the Route¶
route.labels and route.annotations add labels and annotations to the Route. A platform can select the Route that way, for example to register an OpenID Connect client for its host.
0.3.2¶
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.3.1¶
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.3.0¶
Released 2026-10-10.
Changes¶
mkdocs 0.3.0: build on a push through a webhook¶
source.webhook adds the GitLab, GitHub and Generic webhook triggers to the BuildConfig, the Secret that is part of the webhook address, and the RoleBinding that lets the Git server call the webhook without a login. An image trigger restarts the site after the build, so the poller is not needed: set source.pollSchedule to empty. The default stays polling.
0.2.1¶
Released 2026-10-09.
Changes¶
mkdocs 0.2.1: exact refs, no password in a timeout, one build per commit¶
The poller matched any ref ending in the name and took the tag object of an annotated tag, so such a ref was rebuilt on every poll. A timeout of git ls-remote raised with the URL, password included, in the message. A build now names its commit, so a build that fails before the clone is not repeated. A ref such as 1.0 stays a string.
0.2.0¶
Released 2026-10-09.
Changes¶
mkdocs: optional OIDC login and source credentials¶
mkdocs: rebuild when the source branch moves¶
mkdocs: describe the chart, add a test site¶
mkdocs: refuse requests that bypass the login proxy¶
A NetworkPolicy cannot close the site port where another policy of the cluster opens it. With login on, nginx now serves only the proxy in its own pod; probes use /healthz.
mkdocs 0.1.1: accept a cookie secret of any length¶
A secret generated outside the chart can be longer than the 16, 24 or 32 bytes oauth2-proxy accepts; the schema refused it and the render failed. Such a value is now hashed to 32 characters.
mkdocs 0.2.0: roll out without an image trigger¶
The image trigger rewrites the image field of the Deployment and a GitOps tool reverts it, so an Application without an ignore rule never became Synced. The Deployment now names the fixed tag in the cluster registry, and the poller job waits for the build and restarts the pods for the new image.
0.1.0¶
Released 2026-10-09.