fix(eks): cluster.addHelmChart
ignores skipCrds
#31832
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue # (if applicable)
Closes #31831.
Reason for this change
The
kubectl
custom resource lambda was not correctly passing theskipCrds
parameter ofaws_eks.Cluster.addHelmChart
all the way through to the invocation ofhelm
. As such, unexpected behaviour was observed where, even ifskipCrds
wastrue
,helm
running within the lambda would still attempt to install any relevant CRDs as part of the chart.Description of changes
Adds the
skip_crds
argument to the call tohelm
within thehelm_handler
function.Description of how you validated changes
I've run the unit tests and verified no changes. I cannot run the integration tests as I cannot afford the cost of deploying a full EKS cluster into my personal AWS account and I can't link this PR to our org's GitHub as per your guidelines, so I can't deploy into an account our org owns through CI.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license