-
Notifications
You must be signed in to change notification settings - Fork 578
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
📖 add first draft of AWS multitenancy proposal (#1552) #1674
Conversation
Hi @andrewmyhre. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: andrewmyhre The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold |
metadata: | ||
name: my-cluster | ||
spec: | ||
iamRoleArn: arn:aws:iam::123456789:role/CAPARole |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only adding IAM role ARN introduces a confused deputy risk, which is important for some of our users. Would need to support external ID as well, which ideally would be stored separately in a secret to protect what is esentially a pseudo-shared secret.
I'm just going through some docs, and ensuring we can cover the various permutations. Will update tomorrow. |
Hi @andrewmyhre : I've created a Google Doc with proposed changes here: This covers additional use cases important for some of our users, especially around hiding confidential aspects of credentials and caching. |
Let's rally in #1713 if that's ok? |
What this PR does / why we need it: Enable CAPA to reconcile Kubernetes clusters in a multi-tenant/VPC sharing architecture
Which issue(s) this PR fixes :
Partial resolution of #1552