(eks): Reusable Kubectl Provider for imported clusters #14692
Labels
@aws-cdk/aws-eks
Related to Amazon Elastic Kubernetes Service
closed-for-staleness
This issue was automatically closed because it hadn't received any attention in a while.
effort/medium
Medium work item – several days of effort
feature-request
A feature should be added or improved.
p2
It would be great if we could define reusable a Kubectl Provider for imported clusters with
eks.Cluster.fromClusterAttributes
.Use Case
Currently when a cluster is referred to for the first time in a stack it deploys a new NestedStack that contains a single lambda. For accounts with a large number of stacks this can be a problem when getting close to the service limit of 200 stacks per account.
Proposed Solution
Being able to deploy a single provider for a cluster manually, and then do something like
Another potentially solution is to change the
KubectlProvider
from being aNestedStack
to being aConstruct
.Other
There is already a
getOrCreate
function that calls_attachKubectlResourceScope
, but this would only work for an existingeks.Cluster
instance, not one being created usingfromClusterAttributes
This is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered: