You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: for support questions, please first reference our documentation, then use Stackoverflow. This repository's issues are intended for feature requests and bug reports.
I'm submitting a ...
🪲 bug report
🚀 feature request
📚 construct library gap
☎️ security issue or vulnerability => Please see policy
❓ support request => Please see note at the top of this template.
What is the current behavior? If the current behavior is a 🪲bug🪲: Please provide the steps to reproduce
In current README, the aws eks update-kubeconfig without specifying --role-arn will fail. We still need to specify the clusterAdmin IAM role ARN as --role-arn here,.
What is the expected behavior (or behavior of feature suggested)?
aws eks update-kubeconfig succefully executed.
What is the motivation / use case for changing the behavior or adding this feature?
To enhance the user experience.
Please check my sample:
exportclassCdkStackextendscdk.Stack{constructor(scope: cdk.Construct,id: string,props?: cdk.StackProps){super(scope,id,props);// first define the roleconst clusterAdmin =newiam.Role(this,'AdminRole',{assumedBy: newiam.AccountRootPrincipal()});// eks cluster with nodegroup of 2x m5.large instances in dedicated vpc with default configuratrionconstcluster=neweks.Cluster(this,'hello-eks',{clusterName: 'cdk-eks',mastersRole: clusterAdmin});// output the clusterAdmin role arnnewcdk.CfnOutput(this,'clusterAdminRoleArn',{value: clusterAdmin.roleArn})}}
please note I add clusterAdmin.roleArn in the Outputs.
this will be successfully executed with no error and I can immediately kubectl with my cluster like this
kubectl get no
NAME STATUS ROLES AGE VERSION
ip-10-0-150-198.us-west-2.compute.internal Ready <none> 6m57s v1.13.7-eks-c57ff8
ip-10-0-190-37.us-west-2.compute.internal Ready <none> 7m3s v1.13.7-eks-c57ff8
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. associated pull-request, stackoverflow, gitter, etc)
The text was updated successfully, but these errors were encountered:
Synthesize a CloudFormation output that shows the `aws eks update-kubeconfig`
that needs to be executed in order to connect to the cluster. This command will
include the IAM masters role ARN if applicable.
Disable all other outputs by default, but added `outputXxx` options to enable.
Fixes#3664
BREAKING CHANGE: cluster name output will not be synthesized by default. instead we synthesize an output that includes the full `aws eks update-kubeconfig` command. You can enable synthesis of the cluster name output using the `outputClusterName: true` options.
* feat(eks): output update-kubeconfig command
Synthesize a CloudFormation output that shows the `aws eks update-kubeconfig`
that needs to be executed in order to connect to the cluster. This command will
include the IAM masters role ARN if applicable.
Disable all other outputs by default, but added `outputXxx` options to enable.
Fixes#3664
BREAKING CHANGE: cluster name output will not be synthesized by default. instead we synthesize an output that includes the full `aws eks update-kubeconfig` command. You can enable synthesis of the cluster name output using the `outputClusterName: true` options.
* update expectations
* update readme
Note: for support questions, please first reference our documentation, then use Stackoverflow. This repository's issues are intended for feature requests and bug reports.
I'm submitting a ...
What is the current behavior?
If the current behavior is a 🪲bug🪲: Please provide the steps to reproduce
In current README, the
aws eks update-kubeconfig
without specifying--role-arn
will fail. We still need to specify the clusterAdmin IAM role ARN as--role-arn
here,.aws eks update-kubeconfig
succefully executed.To enhance the user experience.
Please check my sample:
please note I add
clusterAdmin.roleArn
in the Outputs.And I got outputs like this
So I can copy the value of
CdkEksStack.clusterAdminRoleArn
from above and run:this will be successfully executed with no error and I can immediately
kubectl
with my cluster like thisPlease tell us about your environment:
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. associated pull-request, stackoverflow, gitter, etc)
The text was updated successfully, but these errors were encountered: