Skip to content

Commit bb3a2fa

Browse files
yankawailexfrei
authored andcommitted
docs(cluster-api): clarify trusted backport image delivery
Signed-off-by: Yan Bondarenko <[email protected]>
1 parent c8f4906 commit bb3a2fa

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

  • packages/system/capi-providers-infraprovider/images/cluster-api-provider-kubevirt

‎packages/system/capi-providers-infraprovider/images/cluster-api-provider-kubevirt/UPSTREAM.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,4 +2,4 @@ The build stays on CAPK v0.1.10, commit `6dbc11c4d0cbfbdcd618566538c10b0d4a07516
22

33
`make image` runs the backported regression tests, builds the manager, and writes the resulting tag and digest to `images/cluster-api-provider-kubevirt.tag`. The InfrastructureProvider reads that file through `spec.deployment.containers[].imageUrl`, supported by CAPI operator v0.19.0. The compressed provider manifest contains the additional VMIM create permission. Keeping the image reference out of the gzip lets the existing image collection, promotion, and nightly mirror code see and rewrite it.
44

5-
The checked-in tag still points at the original upstream image. It is not the patched artifact. Before this draft can be released, an authorized build must publish the new image and replace that pin with its verified tag and digest. Fork CI derives its repository allowlist from the base branch, so adding a new image path here does not by itself authorize publication from a fork.
5+
The checked-in tag still points at the original upstream image, so applying the chart directly from this source tree does not install the backport. The regular main and release builds call this package's `image` target before packaging, and the release workflow commits the resulting digest pin with its other generated artifacts. A release containing the fix must therefore come from that trusted build path. Fork CI derives its repository allowlist from the base branch, so this new image repository requires a maintainer-owned build for pre-merge E2E validation; changing a fork's allowlist does not authorize publication.

0 commit comments

Comments
 (0)