Mikhail Shapirov

AWS CDK team: this issue prevents any customer from leveraging CDK to provision and maintain EKS clusters. We are relying on this support for [CDK EKS Blueprints](https://github.com/aws-quickstart/cdk-eks-blueprints) for example, which...

@elamaran11 the OIDC provider of the imported cluster is supported now. What is not support is OIDC provider creation in case the original cluster does not have OIDC. We should...

@elamaran11 I assume this has been addressed and published in 1.1.0 and 1.2.0, correct?

@elamaran11 could you please review this PR when you get a chance? I am hesitant to _always_ add the awsproxy extension, it could be a config option, but that will...

@elamaran11 can you confirm if awsproxy extension can be added as a separate extensions, e.g. a private add-on that maybe depends on xray ADOT add-on? If so, I suggest posting...

@jdwil it is a good point with Karpenter. Initially there was no restriction with respect to the NTH. It was a separate issue raised against NTH and MNG to add...

Hey @askulkarni2 , this has been addressed a couple minor releases ago, [docs](https://aws-quickstart.github.io/cdk-eks-blueprints/addons/calico-operator/). Calico add-on was deprecated, see [here](https://github.com/aws-quickstart/cdk-eks-blueprints/blob/main/lib/addons/calico/index.ts#L8).

Please see the above comment. The deprecated add-on will be removed in a few releases.

@nthienan @shcherbak CDK has removed support for EKS 1.22 so there is not much we can do on the blueprints side at the moment. The https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_eks.KubernetesVersion.html in CDK goes up...

> @shapirov103 I see this PR was merged, any news for cdk-eks-blueprints? Indeed, it only took half a year to address the PR. However, while it is merged, it is...