-
Notifications
You must be signed in to change notification settings - Fork 492
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
GEP: Backend Protocol Selection #1911
Comments
/assign @dprotaso |
For those following GEP PR is out - #1979 |
Since the GEP already exists and because it's a GEP it seems reasonable to consider this accepted: /triage accepted However, it doesn't seem clear to me that this is something we must sort out prior to GA (though I invite arguments to the contrary) so at least for now we wont consider this a blocker for GA and it will have a lower priority than GA-oriented work: /priority backlog |
ACK Ultimately it's just not clear that this is something we must have for GA 🤔 Since you're working on it anyway, let's go ahead and track it on the board. But we should probably take another look at what it's gonna take to implement and do some planning and prioritization then. |
Leaving this open until this GEP either graduates to standard or is removed from the API. /kind gep |
@robscott: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This issue has not been updated in over 1 year, and should be re-triaged. You can:
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/ /remove-triage accepted |
/kind gep
This is an attempt to separate out the backend protocol selection from GEP-1282. This is similar to how TLS use-cases are being split out into GEP-1897
What would you like to be added:
The ability to express the protocols supported by backends.
Why this is needed:
Not all implementation support automatic protocol selection. Even in some cases protocols are disabled without an explicit opt-in (ie. websockets). Thus application developers need the ability specify the protocol of their applications.
The text was updated successfully, but these errors were encountered: