Remove transient node predicates from KCCM's service controller

[alexanderConstantinescu]

Enhancement Description

• One-line enhancement description (can be used as a release note): Remove transient node predicates from KCCM's service controller
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-network/3458-remove-transient-node-predicates-from-service-controller/README.md
• Discussion Link: Avoid re-syncing LBs for ETP=local services kubernetes#109706 (comment) / Avoid re-syncing LBs for ETP=local services kubernetes#109706 (comment)
• Primary contact (assignee): @alexanderConstantinescu
• Responsible SIGs: sig-network / sig-cloud-provider
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.26
  • Beta release target (x.y): 1.27
  • Stable release target (x.y): 1.30
• Alpha
  • KEP (k/enhancements) update PR(s):
    • KEP-3458: Remove transient node predicates from KCCM's service controller #3460
  • Code (k/k) update PR(s):
    • [KCCM - service controller]: KEP-3458 implementation kubernetes#115204
  • Docs (k/website) update PR(s):
• Beta
  • KEP (k/enhancements) update PR(s):
    • KEP 3458 - 1.28 milestone bump #4088
  • Code (k/k) update PR(s):
  • Docs (k/website) update(s):
• Stable
  • KEP (k/enhancements) update PR(s):
    • [KEP 3458]: 1.29 milestone bump - stable #4257
  • Code (k/k) update PR(s):
    • KEP 3458 - promote to stable kubernetes#122961
  • Docs (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.

[alexanderConstantinescu]

/sig network
/sig cloud-provider

[thockin]

Punting to 1.27

[k8s-triage-robot]

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:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[thockin]

/label lead-opted-in