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
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*
Added new context arn:aws:eks:rrrrr:112233445566:cluster/cluster-xxxxx to /home/boom/.kube/config
76
+
```
77
+
78
+
And now you can simply use `kubectl`:
79
+
80
+
```console
81
+
$ kubectl get all -n kube-system
82
+
NAME READY STATUS RESTARTS AGE
83
+
pod/aws-node-fpmwv 1/1 Running 0 21m
84
+
pod/aws-node-m9htf 1/1 Running 0 21m
85
+
pod/coredns-5cb4fb54c7-q222j 1/1 Running 0 23m
86
+
pod/coredns-5cb4fb54c7-v9nxx 1/1 Running 0 23m
87
+
...
88
+
```
89
+
48
90
### Endpoint Access
49
91
50
92
You can configure the [cluster endpoint access](https://docs.aws.amazon.com/eks/latest/userguide/cluster-endpoint.html) by using the `endpointAccess` property:
The default value is `eks.EndpointAccess.PUBLIC_AND_PRIVATE`. Which means the cluster endpoint is accessible from outside of your VPC, and worker node traffic to the endpoint will stay within your VPC.
60
102
61
-
62
103
### Capacity
63
104
64
105
By default, `eks.Cluster` is created with a managed nodegroup with x2 `m5.large` instances. You must specify the kubernetes version for the cluster with the `version` property.
@@ -208,7 +249,6 @@ When adding capacity, you can specify options for
208
249
which is responsible for associating the node to the EKS cluster. For example,
209
250
you can use `kubeletExtraArgs` to add custom node labels or taints.
0 commit comments