-
Notifications
You must be signed in to change notification settings - Fork 232
Support single Controller Multitenancy #575
Copy link
Copy link
Closed
Labels
help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/activeIndicates that an issue or PR is actively being worked on by a contributor.Indicates that an issue or PR is actively being worked on by a contributor.
Description
Metadata
Metadata
Assignees
Labels
help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/activeIndicates that an issue or PR is actively being worked on by a contributor.Indicates that an issue or PR is actively being worked on by a contributor.
Type
Fields
Give feedbackNo fields configured for issues without a type.
/kind feature
Describe the solution you'd like
Other CAPI providers support single controller multi tenancy, meaning that the controller can use different credentials at runtime when reconciling different workload clusters. It would be cool to have that feature in CAPG.
Anything else you would like to add:
Here are the design docs for other providers