Optionally Disable NodePorts for Service Type=LoadBalancer

[andrewsykim]

Enhancement Description

• One-line enhancement description (can be used as a release note):
  Allow users to disable node ports for Service Type=LoadBalancer. This is useful for bare metal / on-prem environments that rely on VIP based LB implementations.

• Kubernetes Enhancement Proposal: (link to kubernetes/enhancements file, if none yet, link to PR)
  https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/1864-disable-lb-node-ports

• Primary contact (assignee): @andrewsykim

• Responsible SIGs: Network / Cloud Provider

• Enhancement target (which target equals to which milestone):

  • Stable release target 1.24

Allow users to optionally opt-out of node port allocation for Service Type=LoadBalancer. This is useful for VIP-based load balancers that don't require node port and the node port should be blocked for regulatory / compliance reasons.

[andrewsykim]

/sig network

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[kikisdeliveryservice]

Hi @andrewsykim

Will there be any work on this in 1.20?

Thanks!
Kirsten

[andrewsykim]

Yes, @uablrek has a PR open for this already kubernetes/kubernetes#92744, just waiting for an API review

[kikisdeliveryservice]

Thanks @andrewsykim !!

Going forward, please ensure that active issues don't go stale and are properly milestoned as the Release Team tracks Enhancements via these issues. 😺

/milestone v1.20

[kinarashah]

Hi @andrewsykim,

1.20 Enhancement shadow here 👋.

Since your Enhancement is scheduled to be in 1.20, please keep in mind the important upcoming dates:
Friday, Nov 6th: Week 8 - Docs Placeholder PR deadline
Thursday, Nov 12th: Week 9 - Code Freeze

As a reminder, please link all of your k/k PR as well as docs PR to this issue so we can track them.

Thank you!

[kcmartin]

Hello @andrewsykim, 1.20 Docs shadow here.

Does this enhancement work planned for 1.20 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against dev-1.20 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Nov 6th

Also take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!