-
Notifications
You must be signed in to change notification settings - Fork 4k
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: Recent change breaks update of existing clusters #21436
Labels
Comments
resnikb
added
bug
This issue is a bug.
needs-triage
This issue or PR still needs to be triaged.
labels
Aug 3, 2022
github-actions
bot
added
the
@aws-cdk/aws-eks
Related to Amazon Elastic Kubernetes Service
label
Aug 3, 2022
4 tasks
TheRealAmazonKendra
added
p1
and removed
needs-triage
This issue or PR still needs to be triaged.
labels
Aug 4, 2022
mergify bot
pushed a commit
that referenced
this issue
Aug 4, 2022
…#21463) introduced by #21185 Fixes: #21436 ---- ### All Submissions: * [X] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) ### Adding new Unconventional Dependencies: * [X] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-new-unconventional-dependencies) ### New Features * [X] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)? * [X] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)? *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
josephedward
pushed a commit
to josephedward/aws-cdk
that referenced
this issue
Aug 30, 2022
…aws#21463) introduced by aws#21185 Fixes: aws#21436 ---- ### All Submissions: * [X] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) ### Adding new Unconventional Dependencies: * [X] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-new-unconventional-dependencies) ### New Features * [X] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)? * [X] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)? *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Describe the bug
The recent change made in PR #21185 to support logging changes, breaks updates of existing clusters.
Our EKS cluster was created with v2.27 of aws-cdk, and has the following in CF template:
The PR assumes that there are two elements inside
clusterLogging
array.Expected Behavior
The cluster update works without failing.
Current Behavior
Upgrading to CDK 2.35 fails with an error:
Reproduction Steps
To reproduce the bug, create the following cluster with 2.27, deploy, and upgrade CDK to 2.35:
Possible Solution
The resource handler code should check the size of the
clusterLogging
array before accessing the new element.Additionally, although this may be a separate bug, the line 294 from the PR looks suspicious:
It seems that
enabled
will be set totrue
only if it is"false"
in the template?This should also possible change to
Additional Information/Context
No response
CDK CLI Version
2.35.0 (build 5c23578)
Framework Version
No response
Node.js Version
v16.16.0
OS
Linux
Language
Typescript
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: