aws / aws/amazon-eks-pod-identity-webhook

Multi account setup with only one IAM role in k8s account

Open
#39 8 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
691
Forks
202
Avg merge
4h 38m
Merged PRs (30d)
1

Description

**What would you like to be added**:
The current situation is:
- shared K8S cluster in one AWS account
- Team A's pods need to access only team A's AWS account
- Team B's pods need to access only team B's AWS account

The possibility now:
- create IAM role in K8S account *for each team account*
- create IAM role in each team account trusting the k8s account role

Add feature to whitelist which role should be assumed in the namespace level.

**Why is this needed**:

What I want to avoid is to create multiple IAM roles in our K8S account, instead to have one role which should be trusted by all team accounts and then restrict which role to be assumed in the namespace level (That's the current concept in KIAM)

Contributor guide

Open the contributing guide

Research direction

The issue names no files or tests. Start by tracing how namespace-level configuration and IAM role assumptions are represented, then determine how a single Kubernetes-account role could be restricted to approved roles in team accounts; done means the feature supports that restriction without requiring one Kubernetes-account role per team account.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, go, kubernetes
Domain
authorization, cloud, devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.