Support specifying assume_role_arn for Kube cluster matchers
#28282
Conversation
This file contains 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
This PR allows users to assume different AWS roles when interacting with
AWS EKS API. It allows users to proxy EKS clusters in different AWS
accounts using the same Teleport Kubernetes Service.
Example configuration:
```yaml
kubernetes_service:
enabled: true
resources:
- labels:
'a': 'b'
aws:
assume_role_arn: "arn:aws:iam::0987654321:role/KubeAccess"
external_id: "0987654321"
- labels:
'c': 'd'
aws:
assume_role_arn: "arn:aws:iam::123456789012:role/KubeAccess"
external_id: "123456789012"
```
greedy52
approved these changes
Jun 26, 2023
kimlisa
approved these changes
Jun 27, 2023
strideynet
approved these changes
Jun 28, 2023
public-teleport-github-review-bot
bot
removed the request for review
from ravicious
tigrato
added a commit
that referenced
this pull request
Jul 7, 2023
* Support specifiying `assume_role_arn` for Kube cluster matchers
This PR allows users to assume different AWS roles when interacting with
AWS EKS API. It allows users to proxy EKS clusters in different AWS
accounts using the same Teleport Kubernetes Service.
Example configuration:
```yaml
kubernetes_service:
enabled: true
resources:
- labels:
'a': 'b'
aws:
assume_role_arn: "arn:aws:iam::0987654321:role/KubeAccess"
external_id: "0987654321"
- labels:
'c': 'd'
aws:
assume_role_arn: "arn:aws:iam::123456789012:role/KubeAccess"
external_id: "123456789012"
```
* reuse eks token validation
github-merge-queue bot
pushed a commit
that referenced
this pull request
Jul 10, 2023
… (#28832) * Support specifiying `assume_role_arn` for Kube cluster matchers This PR allows users to assume different AWS roles when interacting with AWS EKS API. It allows users to proxy EKS clusters in different AWS accounts using the same Teleport Kubernetes Service. Example configuration: ```yaml kubernetes_service: enabled: true resources: - labels: 'a': 'b' aws: assume_role_arn: "arn:aws:iam::0987654321:role/KubeAccess" external_id: "0987654321" - labels: 'c': 'd' aws: assume_role_arn: "arn:aws:iam::123456789012:role/KubeAccess" external_id: "123456789012" ``` * reuse eks token validation
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR allows users to assume different AWS roles when interacting with AWS EKS API. It allows users to proxy EKS clusters in different AWS accounts using the same Teleport Kubernetes Service.
Example configuration:
Part of #27156