Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Multiple CoreProviders #564

Open
BrennenMM7 opened this issue Jul 9, 2024 · 1 comment
Open

Support Multiple CoreProviders #564

BrennenMM7 opened this issue Jul 9, 2024 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@BrennenMM7
Copy link

User Story

As a dev/operator I would like to be able to install & manage multiple core providers with the CAPI operator. The CAPI project doesn't inherently support multi-tenancy throughout its providers but allows for it to happen if you supply a namespace flag to any type of provider.

I think that the CAPI Operator would be really cool if we can manage multiple providers in different namespaces. This enables different minor versions to be deployed in testing namespaces and promoted without requiring multiple k8s clusters.

I'd love to add more details into this feature request for the project if multi-tenancy support is something the project is interest in pursuing.

Thanks 👍

Anything else you would like to add:

[Miscellaneous information that will assist in solving the issue.]

/kind feature

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 9, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If CAPI Operator contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

2 participants