Skip to content

fix: use custom_role for EKS access entry when configured#177

Merged
stevenolen merged 1 commit intomainfrom
fix-custom-role-eks-access
Mar 11, 2026
Merged

fix: use custom_role for EKS access entry when configured#177
stevenolen merged 1 commit intomainfrom
fix-custom-role-eks-access

Conversation

@stevenolen
Copy link
Collaborator

Description

When a workload uses custom_role, the admin.posit.team IAM role does not exist in the target account. Pass the custom_role ARN as the admin principal for EKS access entries and aws-auth configmap instead of hardcoding admin.posit.team. Falls back to admin.posit.team when no custom_role is configured.

Category of change

  • Bug fix (non-breaking change which fixes an issue)
  • Version upgrade (upgrading the version of a service or product)
  • New feature (non-breaking change which adds functionality)
  • Build: a code change that affects the build system or external dependencies
  • Performance: a code change that improves performance
  • Refactor: a code change that neither fixes a bug nor adds a feature
  • Documentation: documentation changes
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

  • I have reviewed my own diff and added inline comments on lines I want reviewers to focus on or that I am uncertain about

When a workload uses custom_role, the admin.posit.team IAM role does
not exist in the target account. Pass the custom_role ARN as the admin
principal for EKS access entries and aws-auth configmap instead of
hardcoding admin.posit.team. Falls back to admin.posit.team when no
custom_role is configured.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@stevenolen stevenolen requested a review from a team as a code owner March 11, 2026 20:56
@stevenolen stevenolen added this pull request to the merge queue Mar 11, 2026
Merged via the queue into main with commit f664878 Mar 11, 2026
4 checks passed
@stevenolen stevenolen deleted the fix-custom-role-eks-access branch March 11, 2026 21:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants