design-proposal: per-cluster infrastructure backends for tenant Kubernetes clusters - #86
Draft
IvanHunters wants to merge 2 commits into
Draft
IvanHunters wants to merge 2 commits into
IvanHunters wants to merge 2 commits into
Conversation
…brid clusters Supplementary to #9: inventory the tenant-cluster components that assume KubeVirt workers, record what happens to each on a node of another backend, and list non-committal directions and open questions. Signed-off-by: IvanHunters <xorokhotnikov@gmail.com>
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Turn the backend-bound components inventory into a proposal with a position: one CAPI infrastructure provider per tenant cluster, a backend as its own package source with control-plane and node-pool applications, a shared library chart extracted from the KubeVirt charts, a written backend contract, and kubernetes-switchcloud as the second backend. Mixed clusters stay with #9. Signed-off-by: IvanHunters <xorokhotnikov@gmail.com>
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.
Proposes per-cluster infrastructure backends for tenant Kubernetes clusters, supplementing #9 (hybrid Kubernetes clusters).
The position: a tenant cluster uses exactly one CAPI infrastructure provider, chosen at creation. A backend is its own package source with a control-plane application and a node-pool application, built on a shared library chart extracted from today's
kubernetesandkubernetes-nodescharts, and it covers a written contract derived from an inventory of what is KubeVirt-bound today. KubeVirt stays the default backend and existing clusters render the same objects.aenix-org/kubernetes-switchcloud, which already runs OpenStack workers against a Kamaji control plane as a separate chart, is the model for the second backend. Mixed clusters stay with #9; the one point where this differs from the #9 sketches (CAPI providers instead of bypassing CAPI, for single-backend clusters) is called out in the document.Facts are pinned to cozystack
ff52aeb44and the upstream revisions listed in the document.Before review
decisions/directory, or says below why none is needed.Not applicable: this adds a new proposal and does not revise a merged one.
DCO
git commit --signoff).