-
Couldn't load subscription status.
- Fork 5.3k
add ingress provision proposal #1459
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
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Assign the PR to them by writing The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
|
/assign @thockin |
|
@kubernetes/huawei |
|
We should not do anything with this until AFTER the sig deep-dive next week, which is particularly focused on Ingress, and the results of which could modify the landscape. |
|
Would you please give us the feedback of sig deep-dive on this proposal? |
|
The discussion is not done. Unfortunately the deep-dive was not long enough to cover the whole topic. Either @bowei or @nicksardo or I will be publishing the proposal in more detail soon. |
|
@thockin @bowei @nicksardo Any progress? |
|
/assign @bowei for inputs :) |
|
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
|
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
|
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
This is a revised proposal of #275. It built upon the initial "loadbalancer provision" idea of #275 , and combined with ideas and feedbacks from community.
cc @m1093782566 @haibinxie
cc @kubernetes/sig-network-proposals