-
Notifications
You must be signed in to change notification settings - Fork 1.6k
KEP-4006: Updated KEP for 1.35 #5524
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
base: master
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: seans3 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
--> | ||
|
||
1. We will not make *any* changes to current WebSocket based browser/javascript clients. | ||
2. We will not extend the WebSockets communication leg from the API Server to Kubelet (in |
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.
I think is reasonable in order to avoid keeping this KEP and feature gate for longer, this has already an immediate positive impact by allowing the entire ecosystem to use websockets against the apiserver instead of a deprecated protocol like SPDY, with almost zero support for most of the load balancers causing a lot of friction.
/lgtm |
I do think we should resolve the user-visible permissions change related to kubectl exec / attach / portforward - see kubernetes/kubernetes#133515 (comment) The permissions required by kubectl changed from |
New changes are detected. LGTM label has been removed. |
|
||
- `kubectl` environment variables and API Server feature gates are locked to on by default. | ||
- Deprecate `kubectl` environment variables and API Server feature gates for future removal. | ||
- Address RBAC authorization for WebSocket upgrades. The mechanism must be compatible with existing authorization rules for subresources (e.g., `pods/exec`) that are typically enforced on POST requests. |
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.
@liggitt for your comment in kubernetes/kubernetes#133515 (comment) and your code there is unclear to me if you want to rollout this authoritzation compatibility as a separate gate or making this GA but not locked by default during one cycle.
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.
I think we need a separate gate, but we can add a few sentences in this KEP about that gate and it's purpose, since it's sort of prompted by the kubectl
switch to websockets.
I'd like to get that merged as a prereq for indicating work on this KEP is complete / GA
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.
- I have updated the KEP to indicate GA in 1.36.
- I have added a separate feature gate
ForceRBACCreateCheck
for the additionalCREATE
authz check. This functionality is a prerequisite for GA.
Please let me know what you think.
Uh oh!
There was an error while loading. Please reload this page.