fix(eks-public) only use a single node pool pinned to a single AZ and define custom storage classes #335
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… define custom storage classes Signed-off-by: Damien Duportal <damien.duportal@gmail.com>
dduportal
commented
Feb 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related to jenkins-infra/helpdesk#3305
This PR introduces the following changes (already applied manually to validate):
us-east-2aavailability zone where the ACP PVC are created. This node pool is defined with the former autoscaling attributes min/max/desired.us-east-2ato avoid the node pool spawning nodes in another AZ than the PVCsPlease note that I was not able to find a way to extract the availability zone value dynamically but did not try a lot.