On Thu, May 19, 2016 at 8:31 PM, Yuvi Panda <[email protected]> wrote:
> > > On Thu, May 19, 2016 at 10:43 PM, 'Brendan Burns' via Containers at Google > <[email protected]> wrote: > >> That's added by the service account admission controller. It's >> controlled by a flag on the apiserver. >> >> If you remove the service account admission controller from the flag, >> then it should disable that behavior >> > > Yup, but that would remove it from *all* pods. I guess I just want to be > able to launch a specific set of pods without them, since these are running > arbitrary user code (jupyter notebooks, to be exact). Rest of the pods is > not user controlled code, and in fact requires service accounts... > This feature request is being tracked in https://github.com/kubernetes/kubernetes/issues/16779. @erictune posted a workaround <https://github.com/kubernetes/kubernetes/issues/16779#issuecomment-157460294> in the comments for that issue until the feature is implemented. > -- > You received this message because you are subscribed to the Google Groups > "Containers at Google" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/google-containers. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Containers at Google" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-containers. For more options, visit https://groups.google.com/d/optout.
