Justin Nauman

Apologies for the delay, I have not provisioned nor have a current cluster where I have reproduced this. Is this emergent behavior JUST from the 0.10.6 upgrade or was there...

I released an RC tag to Docker Hub as `0.10.7-rc2` with the changes referenced in #189 (a merge of several different efforts). As noted in my previous comment, I am...

Thanks for taking the time to collect those logs! If you have found a way to replicate this it would be very much appreciated. A few questions: - What platform...

I released an 0.10.7-rc3 release that reverts the logic that was introduced in #173 which I believe is the main culprit. The observation about the `Recreate` may be a good...

Yes, a PR would implementing these features would be welcome. There are a few other nuances with how this is done now with the informer which may change the implementation...

@jtblin no real apology necessary, the reality is that you have created something useful that has greatly benefited the community and I thank you for that. I would be happy...

Please don't let the access stop you from contributing. I am going to try and stay on top of some of these PR merges in the meantime. If you have...

I would be pretty surprised if this issue has anything to do with kube2iam directly. If you remove the kube2iam annotation that you have specified (which I'm assuming your kube2iam...

It's true that the actual credential lookup is done by associating the incoming requestor IP with a pod running in the cluster, so actual credentials shouldn't be exposed (unless you...

Not really an issue with Kube2IAM or IAM roles in general, just curious how you determine if it has "proper IAM access"? I typically deploy Kube2IAM in one "pass" of...