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
Remove transient node predicates from KCCM's service controller #3458
Comments
/sig network |
Punting to 1.27 |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/label lead-opted-in |
/retitle Remove transient node predicates from KCCM's service controller |
@thockin @alexanderConstantinescu can one of you confirm that this targeting |
Yes, that is correct and what we've discussed / agreed on the KEP. Maybe @thockin wants to give the final confirmation? |
yes please - this one doesn't have APi so doesn't need an alpha |
Thanks @thockin @alexanderConstantinescu |
Once #3835 merges this enhancement will be ready for inclusion in v1.27 |
With #3835 merged this enhancement is ready to be |
Hi @thockin
Please let me know what PRs in k/k I should be tracking for this KEP. |
@alexanderConstantinescu was there a Docs PR opened against dev-1.27 branch in the k/website repo? If not, please take a look at Documenting for a release - PR Ready for Review to get your PR ready for review as soon as possible. 01:00 UTC Wednesday 22nd March 2023 / 17:00 PDT Tuesday 21st March 2023 is the official deadline. This PR will need a doc review by Tuesday 4th April 2023 to get this into the release. Please reach out to required SIGs to get their review. Thank you! |
Hi @mickeyboxell! I am not sure what features qualify for a doc PR. My PR introduces no user-facing changes, would that still require a doc PR? I am asking because the link provided states:
But there is no "explicit way to use", I guess one can see it as a "performance improvement" of sorts. |
I think a release note is all that should be needed here.
…On Tue, Mar 21, 2023 at 3:48 AM Alexander Constantinescu < ***@***.***> wrote:
Hi @mickeyboxell <https://github.com/mickeyboxell>!
I am not sure what features qualify for a doc PR. My PR introduces no
user-facing changes, would that still require a doc PR? I am asking because
the link provided states:
Do your best to describe your feature and how to use it.
But there is no "explicit way to use", I guess one can see it as a
"performance improvement" of sorts.
—
Reply to this email directly, view it on GitHub
<#3458 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABKWAVEZZ2EJCH65G3XXFBTW5GBPHANCNFSM552KGYSQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Enhancement Description
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(s):Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
The text was updated successfully, but these errors were encountered: