You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Move data-product-controller to a KHoist release signed by the v19.0.5 publisherΒ #6227
The generic first-party image rules accept at most two publish-app revisions, and both slots are in use. This step frees the v8.0.0 slot (467f0758β¦), so v21.3.x can replace it (#6226).
Its only running user is data-product-controller. That runs khoist 9.0.5, whose image is signed by publish-app v8.0.0 (#5683).
Done.#6239 merged at 22:40:59Z (8559debe) and deployed. All three parts of the done condition hold.
1. data-product-controller runs KHoist 9.0.12, signed by publish-app v19.0.5, and is Ready.
The HelmRelease is Ready at data-product-controller.v26 with chart khoist@9.0.12+806cbdd4513f.
The controller, harbour, contract-probe and publisher-review Deployments all run ghcr.io/devantler-tech/khoist@sha256:fb97d7beβ¦, each with 2 of 2 replicas Ready. All 8 pods are Running, with 0 restarts.
The image passes cosign verify with the identity .github/.github/workflows/publish-app.yaml@af042c54β¦, and with the admission policy's own regex.
2. Its live data products still reconcile. The deploy pipeline's verify-data-product-rollout.sh (job 132209657156) reported {"complete":true,"deployments":4,"pods":8,"routes":3,"publicChecks":13,"readinessState":"active","productsInventoried":2,"productsDeclaringUI":0}. The controller acquired its leader lease and started its DataProduct workers, with no error or panic in its logs.
The contract probe's /readyz still returns an occasional 503. Coroot's ContractUnavailable count was 0 to 6 per 30 minutes over the six hours before and after the 22:32Z rollout. So the rate is unchanged, and the probe's code is identical between 9.0.5 and 9.0.12.
3. No running first-party app image is signed by v8.0.0.
ascoachingogvaner, khoist and wedding-app are signed by af042c54.
Activity
docs(data-products): give the 9.0.12 amendment its own rollback
devantler commentedon Nov 13, 2026
Done. #6239 merged at 22:40:59Z (
8559debe) and deployed. All three parts of the done condition hold.1. data-product-controller runs KHoist 9.0.12, signed by publish-app v19.0.5, and is Ready.
data-product-controller.v26with chartkhoist@9.0.12+806cbdd4513f.ghcr.io/devantler-tech/khoist@sha256:fb97d7beβ¦, each with 2 of 2 replicas Ready. All 8 pods are Running, with 0 restarts.cosign verifywith the identity.github/.github/workflows/publish-app.yaml@af042c54β¦, and with the admission policy's own regex.2. Its live data products still reconcile. The deploy pipeline's
verify-data-product-rollout.sh(job 132209657156) reported{"complete":true,"deployments":4,"pods":8,"routes":3,"publicChecks":13,"readinessState":"active","productsInventoried":2,"productsDeclaringUI":0}. The controller acquired its leader lease and started its DataProduct workers, with no error or panic in its logs./readyzstill returns an occasional 503. Coroot'sContractUnavailablecount was 0 to 6 per 30 minutes over the six hours before and after the 22:32Z rollout. So the rate is unchanged, and the probe's code is identical between 9.0.5 and 9.0.12.3. No running first-party app image is signed by v8.0.0.
af042c54.server-cd.af042c54plus its CI. Its node pull fails for the reason in Talos refuses the business-site staging image because its publisher signature is mislabelled in the registry indexΒ #6226.Next: #6228, the slot swap from v8.0.0 to v21.3.x, is unblocked.