-
Notifications
You must be signed in to change notification settings - Fork 295
Add [optional] explicit IAM role specification to NodeDrainer #1123
Add [optional] explicit IAM role specification to NodeDrainer #1123
Conversation
Maybe, not sure, but specifying explicit IAM role could help with #1105 |
@ivanilves Thanks for the fix. Yes, I began to believe we'd need to do this everywhere! Btw, would you mind naming it |
Codecov Report
@@ Coverage Diff @@
## master #1123 +/- ##
==========================================
+ Coverage 35.23% 35.25% +0.01%
==========================================
Files 63 63
Lines 3735 3736 +1
==========================================
+ Hits 1316 1317 +1
Misses 2207 2207
Partials 212 212
Continue to review full report at Codecov.
|
Hey @mumoshu I've followed your advice. Could you please re-review and comment, maybe something more needs to be changed? |
@ivanilves Thanks a lot for taking your time! LGTM. |
Thank you! |
…r-iam-role Add [optional] explicit IAM role specification to NodeDrainer
Add [optional] explicit IAM role specification to NodeDrainer.
If you are happy kube2iam user depending on your setup you may want no AWS credentials being available on pods having no IAM role specifications. At least I believe default access is an evil thing to be avoided.