Skip to content

correct(docs): mark IRSA auth as alpha #708

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

Merged
merged 4 commits into from
Nov 16, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion admin/registries/ecr.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ To access a private ECR registry, Coder needs to authenticate with AWS. Coder
supports two methods of authentication with AWS ECR:

- Static credentials
- IAM roles for service accounts
- **Alpha:** IAM roles for service accounts

### Option A: Provision static credentials for Coder

Expand All @@ -44,6 +44,8 @@ To provision static credentials for Coder:

### Option B: Link an AWS IAM role to the Coder Kubernetes service account (IRSA)

**Note:** This is currently an **alpha** feature.

Coder can use an
[IAM role linked to Coder's Kubernetes service account](https://aws.amazon.com/blogs/opensource/introducing-fine-grained-iam-roles-service-accounts/),
though this is only supported when Coder is running in AWS EKS. This is because
Expand All @@ -57,6 +59,9 @@ is required to provision and inject the required token into the `coderd` pod.

To link an IAM role to Coder's Kubernetes service account:

1. Enable the feature under Manage > Admin > Infrastructure > ECR IAM Role
Authentication.

1. Create an IAM OIDC Provider for your EKS cluster (if it does not already
exist).

Expand Down