Add documentation for using OIDC with EKS #13369
Merged
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
cleverguy25
added
the
impact/no-changelog-required
|
Your site preview for commit 393f3f0 is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-13369-393f3f01.s3-website.us-west-2.amazonaws.com. |
|
hey @cleverguy25 ; Are you ready to merge your PR? |
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 documents how to use our OIDC provider with EKS, similar to our GKE docs. This scenario is basic to show login via token exchange as this is page is part of Pulumi Cloud. Later we should build a full E2E scenario with a pod accessing an ESC environment's secrets and confic specific for ESC.
I also renamed in the left nav from Google Kubernetes Engine to Google GKE as the former wrapped and looked weird. I also fixed some minor issues in the GKE doc.