update iam redpanda agent for eks managed nodepools #17
Conversation
This file contains hidden or 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
ppanagiotis
requested review from
gene-redpanda and
frenchfrywpepper
as code owners
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.
Add the necessary changes to support creating EKS managed node groups for BYOVPC clusters.
The objective is to use EKS managed nodes for all AWS-based clusters. My first attempt was rolled back due to issues affecting BYOVPC clusters, which are outlined in this Slack thread:
https://redpandadata.slack.com/archives/C03FHLV038W/p1740539761199609
I'm now manually retrying the creation of BYOVPC clusters, and this PR includes the required changes to allow successful provisioning.