Skip to content
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

LoadBalancerSku should default to Standard #2414

Closed
CecileRobertMichon opened this issue Sep 28, 2022 · 5 comments · Fixed by #3768
Closed

LoadBalancerSku should default to Standard #2414

CecileRobertMichon opened this issue Sep 28, 2022 · 5 comments · Fixed by #3768
Assignees
Milestone

Comments

@CecileRobertMichon
Copy link
Contributor

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.

@feiskyer
Copy link
Member

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

@CecileRobertMichon
Copy link
Contributor Author

CecileRobertMichon commented Sep 28, 2022

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

/cc @bridgetkromhout

@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 27, 2022
@bridgetkromhout
Copy link

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 5, 2023
@feiskyer feiskyer added this to the v1.27 milestone Jan 31, 2023
@feiskyer
Copy link
Member

/assign @nilo19

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants