-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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 gRPC probe to Pod.Spec.Container.{Liveness,Readiness,Startup}Probe #2727
Comments
/sig network |
/assign |
/sig node |
Tracking issue: kubernetes#2727 Original KEP: kubernetes#1667
Tracking issue: kubernetes#2727 Original KEP: kubernetes#1667
for the quick reference of the reviewer, currently supported solutions:
This solution is in high demand: |
@bowei can you start filing an exception request if you want this in 1.22? It seems very unlikely this feature will make the deadline of tomorrow given that it has not been opted in to the release, is missing PRR, etc. |
/milestone v1.22 |
Tracking issue: kubernetes#2727 Original KEP: kubernetes#1667
Tracking issue: kubernetes#2727 Original KEP: kubernetes#1667
Hi @bowei, 1.22 Enhancements Lead here. We're not removing this from 1.22, but can you address John's comment about updating your kep.yaml metadata to match your KEP README? |
/cc |
Got it, updating. |
@ehashman do we need an exception request? |
It is in the tracking document: https://docs.google.com/spreadsheets/d/1mlui0brYypOAsgS2D13fvcs3At1uMq4i1gWfneq-jxY/edit#gid=1954476102 and was merged in time. Also @ehashman counted it in the Slack message =). We generally not encouraging last minute KEPs so we have a proper planning and be respectful for reviewers time. I think this one is not controversial and it is great that it got merged in time. |
@bowei thanks for leading that, sadly i haven't time to finish my proposal. I did MR for prober long time ago may be commits will be also useful: If you need it, i will rebase and update MR |
@bowei do you working on this now? If not, i would like to take this from here, and base on @PxyUp work kubernetes/kubernetes#89832. |
Hi @bowei 👋, Checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023. Please ensure the following items are completed:
Please let me know if there are any other PRs in k/k I should be tracking for this KEP. As always, we are here to help should questions come up. Thanks! |
Hi @bowei 👋, I’m reaching out from the 1.27 Release Docs team. This enhancement is marked as ‘Needs Docs’ for the 1.27 release. Please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by March 16. For more information, please take a look at Documenting for a release to familiarize yourself with the documentation requirements for the release. |
Thanks, let me take a look. |
Thanks! |
NEXT: Remove gate in 1.29 |
This feature is GAed. There are still several issues to track related tasks or in-discussion issues. |
/remove-label lead-opted-in |
Enhancement Description
Add gRPC probe to Pod.Spec.Container.{Liveness,Readiness,Startup}Probe
k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update PR(s):k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update PR(s):k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update PR(s):The text was updated successfully, but these errors were encountered: