Move EKS CNI configuration from manual step to add-on #23
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
…e terraform provider versions for eks, aks, and gke.
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.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Currently, the step to configure the
WARM_IP_TARGETandWARM_ENI_TARGETconfiguration of the EKS's CNI has been done as a manual step, specifically editing of the DaemonSet. The CNI add-on supports configuring these using the 'additional configuration' option. Updated the Terraform to configure it that way, and updated the readme to remove the manual step and instead describe the changes we're making automatically.This also updates some Terraform providers to the latest, including updating the GKE project to stop to move to the regular
googleprovider completely.Which issue(s) this PR fixes:
Special notes for your reviewer: