-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Add ability to tag network-interface using Launch Template #1563
feat: Add ability to tag network-interface using Launch Template #1563
Conversation
FYI - we'll need to bump the min AWS provider version to 3.53.0 for this change and we'll also want to update an example to show/test/validate its use |
I guess there is no better reviewer than @lisfo4ka who added a similar feature a few days ago :) |
Should I update AWS provider version in my PR or it will be updated by you? I've added example for Managed Node Group launch template. Worker group launch template is already have example with tags |
@antonbabenko What are the next steps? |
Looks good to me, let's hear if @lisfo4ka agrees (hopefully during the next couple of days she replies). |
Hi @nikitacr7 , Some notes - at the moment, we can define tags on the global level via As I can see, your changes will add You can refer to the following PR #450 if you'd like to tag ENIs with For the Also, I believe it's pretty important to include AWS provider version pinning exactly in the same commit with this change. Please, fill free to ask any questions to get more details or let me know if I've misunderstood something. FYI @antonbabenko BR, |
Hi @lisfo4ka @antonbabenko I've updated Terraform code to address all comments. Could you please review it once again? Btw, AWS provider version has been already updated by @antonbabenko in master branch. Best regards, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @nikitacr7,
Thanks for your contribution. Now it looks fine to me. I've applied the changes and everything works properly.
@antonbabenko, approved from my side)
Thanks @nikitacr7 and @lisfo4ka for the review! v17.12.0 has been just released. |
I just want to let you know that changes implemented in the PR don't work due to internal issue at AWS side. AWS support has created issue in container roadmap: aws/containers-roadmap#1496 |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
PR o'clock
Description
The PR should resolve: #1361
Please explain the changes you made here and link to any relevant issues.
Checklist