feat(eks-ci): declare the GitHub Actions OIDC identity provider#2
Merged
devantler merged 1 commit intoJul 10, 2026
Conversation
Step 1 of the EKS CI identity (platform#2326): the account's GitHub OIDC trust anchor, assumed via provider-aws-iam (activated platform#2565). Reconciling it proves the OpenBao bootstrap credential end-to-end and surfaces the account id needed for step 2's role trust policy in status.atProvider.arn. Delete omitted from managementPolicies so a prune can never remove the trust anchor under roles referencing it. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
3 tasks
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
📝 WalkthroughWalkthroughAdds a Crossplane IAM OpenIDConnectProvider for GitHub Actions with configured issuer, client ID, thumbprints, management policies, and provider reference. Adds an EKS CI Kustomization that registers the provider manifest, then updates the root Kustomization to include the EKS CI resources. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
devantler
marked this pull request as ready for review
July 10, 2026 14:23
devantler
added a commit
that referenced
this pull request
Jul 10, 2026
Re-lands #2 (which was accidentally based on the stale scaffold branch rather than main) as a clean commit on top of main. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
devantler
added a commit
that referenced
this pull request
Jul 11, 2026
Re-lands #2 (which was accidentally based on the stale scaffold branch rather than main) as a clean commit on top of main. Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Why
The platform side of the EKS CI identity went live today (platform#2565) but was deliberately left dark — no AWS-side manifests existed, so ksail's EKS smoke test still can't authenticate and its epic stays blocked on this.
What
Declares the account's GitHub Actions OIDC identity provider (the trust anchor every repo-scoped CI role will federate through). Kept to step 1 on purpose: the follow-up role's trust policy must name this provider's exact ARN, which only becomes observable once this reconciles — reconciling it also proves the OpenBao bootstrap credential end-to-end.
Operational note: after merge, the provider's
status.atProvider.arnsupplies the account id; step 2 (theRolewith inline least-privilege policy, trust scoped torepo:devantler-tech/ksail:environment:ci) follows immediately.Part of platform#2326.