[cherry-pick: release-v0.79.x] ci(e2e): fix ko >=v0.19 SBOM push failure on plain-HTTP registry#3630
Merged
tekton-robot merged 1 commit intoJun 30, 2026
Conversation
ko v0.19 unconditionally attempts HTTPS when writing SBOMs, causing the E2E job to fail with "http: server gave HTTP response to HTTPS client" against the plain-HTTP KinD registry (registry.local:5000). Set KO_FLAGS=--insecure-registry in the e2e-matrix env block so that both image pushes and SBOM writes use plain HTTP for the local registry. The flag is already forwarded to `ko apply` via $(KO_FLAGS) in the Makefile apply target, so no Makefile change is needed. Signed-off-by: Jawed khelil <jkhelil@redhat.com> Assisted-by: Claude Sonnet 4.6 (via Cursor) Co-authored-by: Cursor <cursoragent@cursor.com>
4 tasks
Contributor
|
/retest |
Member
|
/approve |
Member
|
/lgtm |
Contributor
Author
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jkhelil The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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
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.
This is a cherry-pick of #3621
Changes
ko v0.19 unconditionally attempts HTTPS when writing SBOMs, which causes
the E2E job to fail with:
against the plain-HTTP KinD registry (
registry.local:5000).Root cause:
ko-build/setup-ko(without a pinnedversion:) picked upko v0.19.1, which introduced mandatory SBOM writes via cosign. cosign uses
HTTPS by default and has no knowledge that
registry.local:5000is a plainHTTP endpoint, so every SBOM push fails.
Fix: set
KO_FLAGS=--insecure-registryin thee2e-matrix.ymljob env.This flag is already forwarded to
ko applyvia$(KO_FLAGS)in theMakefile
applytarget — no Makefile change is required. The flag is scopedto the CI job only; local
make applyagainst production registries (quay.io,ghcr.io) is unaffected.
The fix was verified locally by reproducing the failure against a custom-hostname
plain-HTTP registry and confirming success with the flag set.
Submitter Checklist
make test lintbefore submitting a PRRelease Notes
Made with Cursor