Support for modern (non-classic) global external application load balancer

[segevfiner]

The controller currently creates a classic load balancer. It would be nice to support creating new modern (non-classic) ones instead via e.g. a new ingress class value or otherwise. Is there any reason to keep using the classic ones nowadays?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[segevfiner]

/remove-lifecycle stale