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.
Is this a bug fix or adding new feature?
Bug fix, mostly
What is this PR about? / Why do we need it?
Fixes three small papercuts:
Cleanup TestNameAllocatorLikelyBadName to prevent code coverage flapping
This should prevent code coverage constantly flapping on this test by properly setting up the
existingNames
map. Also, added some comments to make the test more clear.Adjust TestExpiringCache timeouts to decrease CI flakes
This test flakes all the time in CI, especially on the Windows unit tests. I bumped up the sleeps to hopefully combat this, it's set to run in parallel so shouldn't make a significant difference to overall test time.
Standardize deployment methods by removing Kustomize-specific changes
Our helm chart contains two places that are used to magically inject comments into the Kustomize deployment. Remove these to standardize the chart and because they're bad:
In
controller.yaml
, the Kustomize deployment comments out the mode by default, thus running the driver inAll
mode and running the node server on the controller. This is pointless, wastes RAM and CPU, and increases the attack surface.In
serviceaccount-csi-controller.yaml
, the Kustomize deployment has a comment about IRSA. Documenting via comments in the manifests is a horrible practice, EKS Pod Identity is superior to and largely replaces IRSA, and the EKS docs already appropriately document how to use IRSA.What testing is done?
CI/Manual