feature: PodiumD 4.8.5 - #413
Merged
Merged
Conversation
4.8.4 shipped to main via #406 without the Frank!Gateway traffic-class split, so that work has no version slot. Open 4.8.5 as its target. 🤖 Generated by Claude Code with help from Jimbo
Image tag deliberately kept on the 5.0.x line (5.0.1 -> 5.0.2) rather than following the chart's tested-against 5.5.0, so this hop stays a small patch: 5.0.2 adds the configurable BRP verwerkingregister-extension-with- zaaktype fix, nothing else. Chart bumped to 1.0.297 since that's needed to expose brpApi.protocollering.verwerking.extendWithZaaktype as a value at all; its other new feature (zac.auth.enablePkce) is a documented no-op with the 5.0.2 image (PKCE support lands later, in the 5.1.x line). Adds the 4.8.4-to-4.8.5 upgrade guide + values-deltas doc, the images-4.8.5.yaml manifest, and updates images-baseline.yaml and _UPGRADING.md's hop index (also backfills the pre-existing 4.8.0-4.8.4 index gap while at it). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
nginx sidecar was documented as nginx:1.30.2/1.31.1; the chart actually wires the shared global.images.nginx anchor (nginx-unprivileged:1.31.3). images-4.8.4.yaml header also still named an unrelated Open Formulieren bump instead of the Open Beheer one this manifest actually documents. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The 4.8.3→4.8.4 hop is already shipped on main (Open Inwoner/Open Zaak, via #406) without this Open Beheer bump, so this PR's upgrade guide and image manifest are renumbered onto the still-open 4.8.4→4.8.5 hop instead of colliding with the already-published 4.8.3-to-4.8.4-upgrade.md and images-4.8.4.yaml. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
bas-info-nl
marked this pull request as ready for review
August 17, 2026 20:18
bas-info-nl
requested review from
bas-info-nl,
githubjimmeicatt,
jimleitch01,
kees-info and
sytskevanhasselt
and removed request for
bas-info-nl,
githubjimmeicatt and
sytskevanhasselt
August 17, 2026 20:18
bas-info-nl
approved these changes
Aug 17, 2026
bas-info-nl
reviewed
Aug 17, 2026
sytskevanhasselt
approved these changes
Aug 18, 2026
sytskevanhasselt
left a comment
sytskevanhasselt
left a comment
Collaborator
There was a problem hiding this comment.
één kleine opmerking/vraag over de documentatie van de values in docs/_UPGRADE_PATHS/4.8.4-to-4.8.5-values-deltas.md
Maar daar wil ik de approval niet op onthouden
Broken links to the never-created zac-brp-protocollering.md now point to the existing per-vendor protocollering section in 4.8.1-to-4.8.2-gemeente-specific.md. zac-BASICS.md still listed the pre-bump chart/image versions (1.0.251/5.0.1); the upgrading index was missing the 4.8.0 row; and a values.yaml comment still said "0.9.0" where the docs already say "0.9.1 and earlier".
…example extendWithZaaktype was one column right of header/register in the before/after diff example, making it look nested under register instead of a sibling under verwerking.
infojohn
marked this pull request as draft
August 18, 2026 14:28
Collaborator
Author
|
Moved back to draft pending QA verification of the chart version change (per @bas-info-nl's review comment). Will mark ready once verified. |
…example Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Collaborator
Author
|
Deployed and tested on QA (ICATT's Full migration from chart 4.7.3 → 4.8.5 completed, including:
All verified live against the real cluster, not just rendered/templated. A live-cluster pytest suite covering these now lives in podiumd-infra's |
infojohn
marked this pull request as ready for review
August 19, 2026 23:34
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Integration branch for PodiumD 4.8.5. Opened to give work that missed the 4.8.4 cut a version slot — see the branch's opening commit.
Draft until the ZAC chart-version bump (1.0.251 → 1.0.297) is verified on a QA environment — see review discussion.
PR #404 (IN-2004 PABC seed) still targets this branch and hasn't landed yet.
Component versions
Image tag deliberately stays on the 5.0.x ZAC line rather than the chart's tested-against 5.5.0, so this hop stays a small patch — 5.0.2 only adds the configurable BRP verwerkingregister-extension-with-zaaktype fix. Chart 1.0.297 also exposes
zac.auth.enablePkce, but that's a documented no-op with the 5.0.2 image (PKCE support lands later, in the 5.1.x line).What's in this PR
Chart.yaml/values.yaml: version bump to 4.8.5, Open Beheer image0.9.0→0.9.1, ZAC image5.0.1→5.0.2(chart1.0.251→1.0.297), newzac.brpApi.protocollering.verwerking.extendWithZaaktypekey (defaultfalse).4.8.4-to-4.8.5-upgrade.md+ values-deltas guide,images-4.8.5.yamlmanifest, andimages-baseline.yaml/_UPGRADING.mdupdated for the new hop (also backfills the 4.8.0–4.8.4 maintainer-table gap).1.0.251/5.0.1version references inzac-BASICS.md; fixed two links to a doc that was never created, now pointing at the existing per-vendor BRP protocollering section in4.8.1-to-4.8.2-gemeente-specific.md._UPGRADING.md: added the missing 4.8.0 row to the operator-facing upgrade table.Notes
zac.brpApi.protocollering.verwerking.extendWithZaaktype— set totruefor iConnect environments; leave the defaultfalsein all other cases (eServices, 2Secure, or BRP protocollering not enabled).