fix: seed the Deployment with the released lemonade image #3

Merged
binjovi-bot merged 1 commit from seed-image-20261012 into trunk 2026-10-12 14:06:39 +00:00
Owner

The first Deploy (v0.1.0, 40a97fa6…) waited on Argo CD Healthy, and the nginx seed crash-looped on the 8081 probes, so Binjovi never reached the image patch. I set the released image by hand once (kubectl set image, the value the Deploy writes) to break the wait.

This makes the seed the released v0.1.0 image (sha256:8a5ebf34…, cosign verified in release 5f431470) and makes ManifestsTest refuse any other seed. gradle check passes in java-builder:v1.

The first Deploy (v0.1.0, 40a97fa6…) waited on Argo CD Healthy, and the nginx seed crash-looped on the 8081 probes, so Binjovi never reached the image patch. I set the released image by hand once (`kubectl set image`, the value the Deploy writes) to break the wait. This makes the seed the released v0.1.0 image (`sha256:8a5ebf34…`, cosign verified in release 5f431470) and makes `ManifestsTest` refuse any other seed. `gradle check` passes in java-builder:v1.
fix: seed the Deployment with the released lemonade image
All checks were successful
binjovi/ci Binjovi completed the frozen plan
0cc1761bc5
The Binjovi Deploy waits for Argo CD Healthy before it patches the image.
The nginx seed could not pass the probes on management port 8081, so
the first Deploy (v0.1.0) waited forever. ManifestsTest now refuses a
seed that is not a released seanfarm/lemonade image.
binjovi-bot deleted branch seed-image-20261012 2026-10-12 14:06:40 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
sean/lemonade!3
No description provided.