-
Notifications
You must be signed in to change notification settings - Fork 4k
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
feat(eks): default masters role #9464
Conversation
If `mastersRole` is not specified, we now define a default IAM role that can be assumed by anyone (with permissions) in the account. If `mastersRole` is not specified, we now define a default IAM role that can be assumed by anyone (with permissions) in the account. This will allow users to interact with the cluster through `kubectl` by issuing the `aws eks update-kubeconfig` command with the appropriate `--role-arn` option, as specified in the CFN output. Fixes #9463
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just minor docs stuff. Added the do-not-merge
label.
Co-authored-by: Eli Polonsky <[email protected]>
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
If `mastersRole` is not specified, we now define a default IAM role that can be assumed by anyone (with permissions) in the account. This will allow users to interact with the cluster through `kubectl` by issuing the `aws eks update-kubeconfig` command with the appropriate `--role-arn` option, as specified in the CFN output. Fixes #9463 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
If
mastersRole
is not specified, we now define a default IAM role that can be assumed by anyone (with permissions) in the account.This will allow users to interact with the cluster through
kubectl
by issuing theaws eks update-kubeconfig
command with the appropriate--role-arn
option, as specified in the CFN output.Fixes #9463
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license