Skip to content

Move data-product-controller to a KHoist release signed by the v19.0.5 publisherΒ #6227

Closed
1 of 1 issue completed

Description

@devantler

πŸ€– Generated by the Agentic Engineer

Why

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).

What

Done when

  • data-product-controller's pods run a khoist image signed by publish-app v19.0.5 and are Ready.
  • Its live data products still reconcile.
  • No running first-party image is signed by v8.0.0, checked across every running ghcr.io/devantler-tech/* app image.

Part of #6226

Activity

  1. added theissue type on Nov 13, 2026
  2. moved this to πŸƒπŸ»β€β™‚οΈ In Progress in 🌊 Project Boardon Nov 13, 2026
  3. moved this from πŸƒπŸ»β€β™‚οΈ In Progress to βœ… Done in 🌊 Project Boardon Nov 13, 2026
  4. devantler commented on Nov 13, 2026

    @devantler
    ContributorAuthor

    πŸ€– Generated by the Agentic Engineer

    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.

    Next: #6228, the slot swap from v8.0.0 to v21.3.x, is unblocked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Fields

    Priority

    None yet

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions