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

Can't redeploy EKS bulk import optional stack #3480

Open
patchwork01 opened this issue Oct 14, 2024 · 0 comments
Open

Can't redeploy EKS bulk import optional stack #3480

patchwork01 opened this issue Oct 14, 2024 · 0 comments
Labels
bug Something isn't working on-hold

Comments

@patchwork01
Copy link
Collaborator

patchwork01 commented Oct 14, 2024

Description

We can't remove and then redeploy the EKS bulk import optional stack. The EKS cluster is deployed with a custom resource provider (see cluster-resource-provider.ts). This includes lambdas and a waiter state machine, that each have a log group. When the optional stack is added and then removed, those log groups are retained but are no longer managed by the CDK. When we add the optional stack back into the Sleeper instance, it fails to deploy because those log groups already exist.

Steps to reproduce

  1. Deploy an instance of Sleeper
  2. Enable optional stack EksBulkImportStack, wait for CDK deployment
  3. Disable optional stack EksBulkImportStack, wait for CDK deployment
  4. Enable optional stack EksBulkImportStack
  5. See CDK deployment fails because a log group already exists

Expected behaviour

We should be able to disable and re-enable the optional stack as many times as we like.

We need a way to configure the log groups on the custom resource provider lambdas and waiter state machine. We've raised an issue for this on the CDK GitHub repository:

Background

Split from:

Related to:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working on-hold
Projects
None yet
Development

No branches or pull requests

1 participant