Mikhail Shapirov

Example of creating unencrypted cluster: ```typescript const stack = blueprints.EksBlueprint.builder() .account("123456789012") .region("us-east-1") .useDefaultSecretEncryption(false) .build(app, "east-test-1"); ```

@marcuskrantz there was a similar issue against gitlab previously and we worked through the format of the credentials to make it work. Have you validated if you can bootstrap that...

@marcuskrantz I suspect it is a defect that may have been caused by the secret name containing "/" characters. The kubernetes secret name that is created through the CSI Secret...

It is a workaround, I will use this issue to fix the secret name mapping issue.

Looks like a candidate for the patterns repo. I am unclear on the strategy related to the persistent volumes. Is the expectation to back them up and restore for the...

@daveschmidt86 thank you for submitting the issue. I was not able to reproduce it with the versions you specified. Tried with 1.0.0 and 1.0.1 and different CDK versions as well....

@daveschmidt86 were you able to reproduce this after the initial occurence?

This will be fixed by exposing the disk size parameter. If there is anything else of similar nature that you would like to add to the node group configuration, please...

@engel80 this has been supported for a couple of patch releases. You can use labels like this: ```typescript const clusterProvider = new blueprints.GenericClusterProvider({ version: KubernetesVersion.V1_21, managedNodeGroups: [ { id: "mng1",...

@daveschmidt86 was Calico used on a new clean cluster (new provisioning) or was it applied to an existing cluster? The reason why I ask: we are getting a flood of...