This repository has been archived by the owner on Oct 24, 2023. It is now read-only.
chore: use Standard LoadBalancer as default #2998
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reason for Change:
This PR changes default cluster configuration enforcement so that Standard is the LoadBalancer SKU type if the user does not declare a
loadBalancerSku
value in thekubernetesConfig
configuration object."Basic"
LoadBalancer configuration is no longer appropriate as a default for cluster configurations, as it precludes running LoadBalancer-backed Kubernetes services behind multiple node pool-enabled clusters.Folks who want to continue using the legacy
"Basic"
LoadBalancer type will have to explicitly declare so in their api model:Issue Fixed:
Fixes #2952
Requirements:
Notes: