search

aws-quickstart / cdk-eks-blueprints

AWS Quick Start Team
Apache License 2.0
450 stars 199 forks source link

Config-driven definion for the EKS blueprint CDK #805

Open haofeif opened 1 year ago

haofeif commented 1 year ago

Describe the feature

The current way of deploying EKS cluster via bluerpint has to have the CDK knowledge. From specifying the subnets of the eks, specifying the node group size and instance type, and fargate profile.

However, for some of the users, particularly in a self-service fashion, all of these could be configuration like YAML or JSON. The users/application team who request for an EKS cluster only need to know what information to put in as a configuration, instead of knowing the details of the CDK code.

Therefore, we recommend providing examples/features that is config-driven via YAML/JSON to specify the configuration details of the EKS cluster without the need to know CDK.

Use Case

This is for a platform team who has multiple EKS clusters for each application team, each application team has its own dedicated EKS cluster. But a lot of them do not have to understand cdk, as all they need is an EKS cluster. The config driven definition could give them the opportunity to request a new EKS cluster with the configuration they need following the documentation provided to them without the need to know CDK

Proposed Solution

The solution can be an example or a dedicated module that convert the config (yaml /json) into CDK code that deploy the EKS cluster via the EKS blueprint

Other Information

No response

Acknowledgements

CDK version used

v2.89

EKS Blueprints Version

No response

Node.js Version

latest version

Environment details (OS name and version, etc.)

Mac OS

gyalai-aws commented 1 year ago

+1

github-actions[bot] commented 9 months ago

This issue has been automatically marked as stale because it has been open 60 days with no activity. Remove stale label or comment or this issue will be closed in 10 days

jsamuel1 commented 7 months ago

This would be useful for many enterprise platform scenarios.

github-actions[bot] commented 4 months ago

This issue has been automatically marked as stale because it has been open 60 days with no activity. Remove stale label or comment or this issue will be closed in 10 days

github-actions[bot] commented 1 month ago

This issue has been automatically marked as stale because it has been open 60 days with no activity. Remove stale label or comment or this issue will be closed in 10 days