馃摉 docs: add proposal for OCI publishing - #14033
Open
richardcase wants to merge 1 commit into
Open
Conversation
This adds a new proposal (CAEP) for adding OCI publishing to core CAPI. The initial use cases are clusterctl and GitOps via CAPI Operator. Signed-off-by: Richard Case <richard.case@omniva.com>
kubernetes-prow
Bot
added
area/release
kubernetes-prow
Bot
added
size/L
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found 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
1 participant
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.
What this PR does / why we need it:
This adds a new proposal (CAEP) for adding support for packaging the CAPI manifests as OCI and publishing to registry.k8s.io.
It covers 2 initial use cases:
clusterctl init/upgradeNOTE: this deliberately doesn't cover changing the templating mechanism away from envsubst and doesn't cover Argo/Flux applying the manifests directly.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Relates #13729
/area release
/area clusterctl