Roadmap¶
Milestone state comes from the tests themselves, not from a list kept by hand — the tests are what decide whether a milestone is met, so anything else is a copy waiting to drift.
Milestones¶
| Milestone | Applies to | State | |
|---|---|---|---|
| M0 | Reproducible recipe: the build produces the Kong version it declares | every image | 🟢 reached |
| M1 | Source parity with the extracted 2.0.3 baseline, minus six declared differences | Kong < 3, kong-oidc image | 🟢 reached |
| M2 | Kong 2.x image is publishable (pre-push gate) | Kong < 3 | 🟢 reached |
| M2b | Kong 2.x variant carries a maintained OIDC implementation | Kong < 3, oidcify image | 🟢 reached |
| M3 | A replacement is chosen for oidc on Kong 3.x — oidcify | Kong >= 3 | 🟢 reached |
| M3b | A replacement is chosen for jwt-keycloak on Kong 3.x | Kong >= 3 | 🟡 declared outstanding (XFAIL) |
| M4 | Kong 3.x image is publishable | Kong >= 3 | 🟡 declared outstanding (XFAIL) |
Open work¶
High¶
Medium¶
| Item | Unblocks | |
|---|---|---|
BL-08 |
Warm up the oidcify plugin server on start | — |
BL-11 |
Review oidcify's maintenance once a quarter | — |
Finished¶
BL-03Pin the base image by digest, not by tagBL-04Publish the image that was tested, not a rebuild of itBL-06Add OCI labels and build provenanceBL-09Scopepackages: writeto the job that publishesBL-10Pin GitHub Actions by SHABL-12Excludescripts/anddocs/from the build contextBL-13plugins/exists only on diskBL-14Document wherelua-resty-jwtandlua-resty-cookiecome fromBL-15CODEOWNERS and branch protection
5 open, 9 finished, 5 of 7 milestones reached.