-
Notifications
You must be signed in to change notification settings - Fork 1.1k
There will be changes to permissions of the default service account in 1.6 #400
Comments
@errordeveloper any details on the intended changes anywhere? |
The toplevel meta-issue is kubernetes/enhancements#2,
but I'm not able to dig out anything more specific right now...
…On Tue, 24 Jan 2017 at 13:57 Paul Bellamy ***@***.***> wrote:
@errordeveloper <https://github.com/errordeveloper> any details on the
intended changes anywhere?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#400 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAPWS4DPsVQ_C6nTRtMyJ1X1Tzvielgaks5rVgNegaJpZM4LsLw3>
.
|
From talking to @luxas, I figure we will need to create some RBAC API object from the launch generator. There is code in |
Also, there also a problem that RBAC goes from Alpha to Beta, namely RBAC for rules for v1.5 won't have the same |
both alpha and beta APIs exist in 1.6, and a role created with v1alpha1 will also be accessible from the v1beta1 API |
@liggitt thanks very much! |
I need a list of permissions that Flux requires, like what we have for Net, any chance someone could look into it? |
Presently, we need:
I have guessed some actions / objects; we'll need to test them out of course. |
I think |
This should had be closed a while ago, however it'd be good to refine permissions we ask for – #850. |
See weaveworks/scope#2149 for details.
The text was updated successfully, but these errors were encountered: