-
Notifications
You must be signed in to change notification settings - Fork 431
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
Multi-tenancy within one manager instance #586
Comments
related to #583 |
Hi, we're chatting about the AWS proposal today at 17:30 UTC. Ping me on slack [at]naadir if you want the invite with the Zoom ID & password. |
This is really interesting, especially for highly regulated environments like banks (as the CAPA proposal mentions) and to companies offering an internal platform/self service for their engineering teams to use. Banks are an interesting one, as even sharing a management cluster may not be allowed....depending in what era the security controls still reside in. |
/priority important-longterm |
/reopen this isn't actually implemented yet |
@CecileRobertMichon: Reopened this issue. In response to this:
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/test-infra repository. |
/assign |
/assign |
/kind feature
Describe the solution you'd like
Provide multi-tenancy within the same instance of a CAPZ controller, rather than one instance per credential set.
CAPA issue: kubernetes-sigs/cluster-api-provider-aws#1552
CAPA multitenancy proposal: https://docs.google.com/document/d/1vwjvWc-RIZfwDXb-3tW4gKBOaPCKhripfhXshOmB5z4/edit#heading=h.13bi7vgop9tn
TODOs:
The text was updated successfully, but these errors were encountered: