Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(aws-eks): Cluster creation fails due to cfn-response #14069

Closed
Marakai opened this issue Apr 9, 2021 · 4 comments
Closed

(aws-eks): Cluster creation fails due to cfn-response #14069

Marakai opened this issue Apr 9, 2021 · 4 comments
Assignees
Labels
@aws-cdk/aws-eks Related to Amazon Elastic Kubernetes Service guidance Question that needs advice or information. response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days.

Comments

@Marakai
Copy link

Marakai commented Apr 9, 2021

Issue:

Creation of minimal EKS cluster fails due to time-out of stack creation. The cluster is correctly created, but then the final steps don't finish. The error is

Reproduction Steps

from aws_cdk import \
    (
    core as cdk,
    aws_ec2 as ec2,
    aws_eks as eks,
    aws_iam as iam,
)


class ClustercdkStack(cdk.Stack):

    def __init__(self, scope: cdk.Construct, construct_id: str, **kwargs) -> None:
        super().__init__(scope, construct_id, **kwargs)

        vpc = ec2.Vpc(self, 'EKSVpc',
            subnet_configuration = [
                ec2.SubnetConfiguration(
                    subnet_type=ec2.SubnetType.ISOLATED,
                    name='EKS',
                    cidr_mask=21
                ),
            ])

      
        cluster_admin = iam.Role(
            self, 'ClusterAdmin',
            assumed_by=iam.AccountRootPrincipal(),
            role_name='eks_cdk_admin'
        )

        eks_cluster = eks.Cluster(self, 'EKSCluster',
                                  vpc=vpc,
                                  cluster_name='cdkcluster',
                                  default_capacity=0,
                                  vpc_subnets=vpc.select_subnets(subnet_type=ec2.SubnetType.ISOLATED,
                                                                     one_per_az=True).subnets,
                                  default_capacity_type=eks.DefaultCapacityType.NODEGROUP,
                                  endpoint_access=eks.EndpointAccess.PRIVATE,
                                  version=eks.KubernetesVersion.V1_19,
                                  masters_role=cluster_admin
                                  )

Create a simple Python CDK app, use code above and deploy the usual way (bootstrap/synth/deploy)

What did you expect to happen?

Stack should complete with deployed cluster.

What actually happened?

In step 'EKSClusterAwsAuthmanifest I receive

CloudFormation did not receive a response from your Custom Resource. Please check your logs for requestId [5a9c5fbd-6d88-452e-ad77-eafe92992b41]. If you are using the Python cfn-response module, you may need to update your Lambda function code so that CloudFormation can attach the updated version.

This is documented to occur due to outdated lambda function - which I have no control over in this context, as it's generated somewhere in the bowels of CDK, isn't it?

Environment

  • CDK CLI Version : 1.97.0
  • Framework Version:
  • Node.js Version: 14.6.1
  • OS : MacOS Big Sur 11.2.3
  • Language (Version): Python 3.9.2

Other


This is 🐛 Bug Report

@Marakai Marakai added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Apr 9, 2021
@github-actions github-actions bot added the @aws-cdk/aws-eks Related to Amazon Elastic Kubernetes Service label Apr 9, 2021
@Marakai Marakai changed the title (aws-eks): Cluster creation fails due to cfn-restore (aws-eks): Cluster creation fails due to cfn-response Apr 9, 2021
@iliapolo
Copy link
Contributor

iliapolo commented Apr 9, 2021

@Marakai Unfortunately there is currently a limitation around creating clusters in isolated VPCs.

See #12171 for some more details.

@iliapolo iliapolo added guidance Question that needs advice or information. response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. and removed bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Apr 9, 2021
@Marakai
Copy link
Author

Marakai commented Apr 9, 2021

I see. Thanks. I'll keep an eye on updates and will work around it for now.

@Marakai Marakai closed this as completed Apr 9, 2021
@github-actions
Copy link

github-actions bot commented Apr 9, 2021

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

@guybagi435
Copy link

@Marakai did you manage to solve the issue?
I'm currently struggling with the same exact issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@aws-cdk/aws-eks Related to Amazon Elastic Kubernetes Service guidance Question that needs advice or information. response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days.
Projects
None yet
Development

No branches or pull requests

3 participants