kube2iam
kube2iam copied to clipboard
jtblin
Looking for maintainers
First, I want to apologise for the delay in approving pull requests that provide necessary bug fixes and new features for this project. I know kube2iam has been of great assistance to the Kubernetes community and it needs to continue to get attention but the reality is that I don't have the bandwidth anymore to support this project. Moreover I am not using kubernetes directly anymore which makes it hard for me to stay up to date, perform testing, etc. as I have moved on to a different role.
That being said, I am looking for maintainers who would be willing to review and merge pull requests, and take care of releasing the docker image. I am looping in some people here who have been contributing code in the past and provide feedback and support to users: @mikkeloscar, @jrnt30 but I'm open to others as well. The number of issues and requests is not very high so I don't expect this to be too much of a time sink but with more than 2M downloads for the image, it is important that we ensure good quality reviews for new code.
Please respond to this thread or contact me via email in case you'd be interested.
@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 to try and help maintain the project but would want to find an additional person to perform those duties with.
Thanks again for the work, I had DMd you a bit ago on the Kubernetes slack but wasn’t sure as to your email. I’m JRNT30 just about everywhere
I have a vested interest in ensuring the continuity of kube2iam, so I'll put my hand up.
Awesome, thanks! I'm on leave for one week but will follow-up when I'm back.
On Fri., 13 Apr. 2018, 10:00 pm Paul Saunders, [email protected] wrote:
I have a vested interest in ensuring the continuity of kube2iam, so I'll put my hand up.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jtblin/kube2iam/issues/132#issuecomment-381144671, or mute the thread https://github.com/notifications/unsubscribe-auth/ABUxrhrv4QiLNdCc6oS91_T8nelMiCzOks5toK-IgaJpZM4S6iFP .
@jtblin any news? there are some serious issues here that needs to be solved.
@SharpEdgeMarshall you seem to have a ton of experience with Go, Kubernetes, etc. would you be happy to be a maintainer. Only @jrnt30 have raised his hand so far (thanks a ton!) and it'd be great to have more people who can help reviewing issues and PRs!
I too have a vested interest in the continuity of kube2iam, so I would be happy to contribute & maintain if required.
@jtblin Sure, as an active user of kube2iam in production I would be happy to maintain and contribute to it.
@jtblin I use kube2iam in production too, and would be happy to help maintain it
If you are still looking, we also run kube2iam (new yet production, but moving that way) , on EKS. Can add as a maintainer, have a team here who is actively involved / invested in IAM in kubernetes for our services.
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 some broader architectural discussions please post a PR for a design doc or hit me up on the K8 slack @jrnt30. I would also be open to hosting a quick video chat with people to feel out what they are looking to get out of contributing and the direction they would want to see with the project
@jtblin Happy Tuesday!
I have been running kube2iam in production at scale for some time and would also love to help out the community. It is an essential part of our platform, so I would have adequate bandwidth to help support the project.
Have been keeping an eye on this project along with AWS roadmap for pod level IAM role support that's supposedly coming. Some great work here 👍
Have you considered handing the project over to k8s SIGs? https://github.com/kubernetes-sigs
@jtblin @jrnt30 Our team has been using this in production for over a year now and have been very happy with it. We'd be happy to help maintain for the next few months until AWS finishes and fully upstreams https://github.com/aws/containers-roadmap/issues/23
