Allow policy to control which namespaces are able to assume which roles

[pingles]

We're in the process of experimenting with running a cluster where many different teams would be able to deploy their different apps onto the same cluster. We'd like to be able to control which processes are able to assume which roles- so a role which allows access to a particular KMS resource would only be available to pods running in the kube-system namespace, for example.

Is anyone else working on this (or interested in something like it)?

[SleepyBrett]

This just got merged the other day.

[struz]

This is in release 0.4.0

[pingles]

Awesome, sorry for the dupe- I was looking through other issues and couldn't see anything obvious. Will try out the updated release asap. Thanks for all your work on this- a super useful project for us!!

…

On Tue, 14 Mar 2017 at 00:48, Matt Whittington ***@***.***> wrote: This is in release 0.4.0 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#57 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAEfjn8fRuegonkv4_8om0a6QBZgwukks5rlePIgaJpZM4MYPo5> .