cloud-provider-azure icon indicating copy to clipboard operation
cloud-provider-azure copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

LoadBalancerSku should default to Standard

Open CecileRobertMichon opened this issue 2 years ago • 2 comments

ClusterConfig defaults loadBalancerSku to basic: https://cloud-provider-azure.sigs.k8s.io/install/configs/#cluster-config.

On 30 September 2025, Basic SKU public IP addresses will be retired in Azure. You can continue to use your existing Basic SKU public IP addresses until then, however, you'll no longer be able to create new ones after 31 March 2025.

Basic SKU is being retired. We should not be defaulting to basic for LB and public IP SKUs.

Standard SKU public IP addresses offer significant improvements, including:

  • Access to a variety of other Azure products, including Standard Load Balancer, Azure Firewall, and NAT Gateway.
  • Security by default—closed to inbound flows unless allowed by a network security group.
  • Zone-redundant and zonal front ends for inbound and outbound traffic.

Even if the retirement date is 3 years away, we should consider making this change now as the default value should reflect the recommended best practices in Azure.

CecileRobertMichon avatar Sep 28 '22 00:09 CecileRobertMichon

@CecileRobertMichon thanks for raising this issue. Are there any graceful update support plans in capz or aks-engine?

feiskyer avatar Sep 28 '22 06:09 feiskyer

CAPZ never supported basic LBs. AKS Engine will be deprecated long before retirement.

/cc @bridgetkromhout

CecileRobertMichon avatar Sep 28 '22 16:09 CecileRobertMichon

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

k8s-triage-robot avatar Dec 27 '22 17:12 k8s-triage-robot

/remove-lifecycle stale

bridgetkromhout avatar Jan 05 '23 03:01 bridgetkromhout

/assign @nilo19

feiskyer avatar Apr 20 '23 07:04 feiskyer