Mikhail Shapirov

We will provide an option to pass the role in a more intuitive way. You should not extend a stack and use a blueprint within that stack. Blueprints framework creates...

Hello @bnaydenov, it is in progress now, I will include either in the next maintenance release or minor which should be within 2 weeks.

Will update this issue shortly with an approach. Working on it.

Hello @jagadeeshmaneri , my apologies for not replying sooner. The reason why this was missed is because it does not appear to be a blueprints issue. Rather it is a...

@vumdao as far as I remember we discussed it in #423 and the solution with overrides seemed to work for you. The version set to a specific CDK version is...

@softmates this issue is resolved in 1.4.0. I will keep it open for a bit to allow for testing, will close shortly.

@armujahid current version of CDK does not have this support ootb. The approach that you could take is to pass the version as `KubernetesVersion.of("1.24")`. We can apply a change to...

@praveenperera Grouping of stacks for deployment pipeline is generally recommended with the waves feature of pipelines: https://aws-quickstart.github.io/cdk-eks-blueprints/pipelines/#adding-waves With this you can define a staging wave and add two clusters to...

@softmates we can relax the assertion however there is logic that relies on known nodegroups to add the managed policy to the node group role For example we add `AmazonSSMManagedInstanceCore`...

Removing the cluster encryption key now will cause the same issue for clusters that were provisioned after 1.4.x. I can add an explicit option to leave cluster unencrypted if that...