From 724aa170ffa68bbe5d2079d6027fca6fe5897a0a Mon Sep 17 00:00:00 2001 From: Otavio Macedo Date: Thu, 11 Nov 2021 19:44:41 +0000 Subject: [PATCH] chore(eks): clarified the usage of the `vpcSubnets` property (#17420) Closes #17023. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license* --- packages/@aws-cdk/aws-eks/README.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/packages/@aws-cdk/aws-eks/README.md b/packages/@aws-cdk/aws-eks/README.md index 493168fa2689a..8f2f122af6134 100644 --- a/packages/@aws-cdk/aws-eks/README.md +++ b/packages/@aws-cdk/aws-eks/README.md @@ -102,8 +102,8 @@ The following is a qualitative diagram of the various possible components involv ```text +-----------------------------------------------+ +-----------------+ - | EKS Cluster | kubectl | | - | ----------- |<-------------+| Kubectl Handler | + | EKS Cluster | kubectl | | + |-----------------------------------------------|<-------------+| Kubectl Handler | | | | | | | +-----------------+ | +--------------------+ +-----------------+ | @@ -516,6 +516,9 @@ new eks.Cluster(this, 'HelloEKS', { If you do not specify a VPC, one will be created on your behalf, which you can then access via `cluster.vpc`. The cluster VPC will be associated to any EKS managed capacity (i.e Managed Node Groups and Fargate Profiles). +Please note that the `vpcSubnets` property defines the subnets where EKS will place the _control plane_ ENIs. To choose +the subnets where EKS will place the worker nodes, please refer to the **Provisioning clusters** section above. + If you allocate self managed capacity, you can specify which subnets should the auto-scaling group use: ```ts