-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add authz flags #1357
Add authz flags #1357
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question
@@ -384,6 +384,9 @@ type KubeAPIServerConfig struct { | |||
KubeletPreferredAddressTypes []string `json:"kubeletPreferredAddressTypes,omitempty" flag:"kubelet-preferred-address-types"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure why we would add something to the API, and not wire it up. The API now has stuff in it that does not work. Kind of confusing for me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 here - what gives?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@justinsb explained that we can have API values on components that don't have legacy yaml stuff, and it will add the flags automatically.
If this is unblocking a few devs can we maybe
|
It would also be great if you could add the various authentication flags? e.g. |
@kris-nova @chrislovecnm so you could specify these flags by putting this into your cluster spec:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need any tests or just list it as alpha?
@@ -384,6 +384,9 @@ type KubeAPIServerConfig struct { | |||
KubeletPreferredAddressTypes []string `json:"kubeletPreferredAddressTypes,omitempty" flag:"kubelet-preferred-address-types"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@justinsb explained that we can have API values on components that don't have legacy yaml stuff, and it will add the flags automatically.
@@ -384,6 +384,9 @@ type KubeAPIServerConfig struct { | |||
KubeletPreferredAddressTypes []string `json:"kubeletPreferredAddressTypes,omitempty" flag:"kubelet-preferred-address-types"` | |||
|
|||
StorageBackend *string `json:"storageBackend,omitempty" flag:"storage-backend"` | |||
|
|||
AuthorizationMode *string `json:"authorizationMode,omitempty" flag:"authorization-mode"` | |||
AuthorizationRBACSuperUser *string `json:"authorizationRbacSuperUser,omitempty" flag:"authorization-rbac-super-user"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
note that the superuser flag was removed post-1.5. not sure you want to add it just for the 1.5 release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! But I think people will want to set it in 1.5, so we have to map it.
We aren't wiring them up now, but this unblocks people that want to have a go.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
We aren't wiring them up now, but this unblocks people that want to have
a go.
This change is