[AKS] graduate dual-stack to GA#25256
Conversation
|
AKS |
FumingZhang
left a comment
There was a problem hiding this comment.
For the lint failure, please update src/azure-cli/azure/cli/command_modules/acs/linter_exclusions.yml to bypass the check on load_balancer_managed_outbound_ipv6_count.
Please also update the PR title, as it will be included in the cli release note.
|
|
||
| def test_configure_load_balancer_profile(self): | ||
| managed_outbound_ip_count = 5 | ||
| managed_outbound_ipv6_count = 4 |
There was a problem hiding this comment.
This set of profile (hybrid_2020_09_01) is using a legacy API version 2020-11-01, does ipv6 related properties introduced at that time? If not, I think we'd better not touch these test files.
There was a problem hiding this comment.
so 2020-11-01 does not have IPv6 changes but the test failed when I didn't add it because of the call to configure_load_balancer_profile ... should I just pass None instead?
There was a problem hiding this comment.
Yes, should ensure that not setting this field (pass None) wouldn't break the function.
Signed-off-by: Tyler Lloyd <tyler.lloyd@microsoft.com>
There was a problem hiding this comment.
LGTM, queued a pipeline to test newly added test cases.
| else: | ||
| if ( | ||
| self.get_load_balancer_managed_outbound_ip_count() or | ||
| self.get_load_balancer_managed_outbound_ipv6_count() or |
There was a problem hiding this comment.
This validation is not included in aks-preview
There was a problem hiding this comment.
I think that's an oversight then. we should raise an error if outbound type is UDR and there is IPv6 count defined similar to the _ip_count parameter. I added a unit test to cover this
|
|
||
| def test_configure_load_balancer_profile(self): | ||
| managed_outbound_ip_count = 5 | ||
| managed_outbound_ipv6_count = 4 |
There was a problem hiding this comment.
Yes, should ensure that not setting this field (pass None) wouldn't break the function.
Please describe the feature of the new parameters more detail in the history notes, it is better to have a separate record for each parameter~ |
@zhoxing-ms updated the PR description with more details for each parameter. I don't see a HISTORY.rst for the GA cli so let me know if the details should go anywhere else. |
Since the current history notes cannot support the display of the list format, please write a separate record for each new parameter |
@zhoxing-ms |
|
@tyler-lloyd I have refined the description of history notes, could you help to see if it meets your expectations? |
|
made one small update to the --pod-cidrs description but lgtm |
| - AZURECLI/2.44.1 azsdk-python-azure-mgmt-containerservice/21.1.0 Python/3.10.6 | ||
| (Linux-5.15.0-1031-azure-x86_64-with-glibc2.35) | ||
| method: PUT | ||
| uri: https://management.azure.com/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/clitest000001/providers/Microsoft.ContainerService/managedClusters/cliakstest000002?api-version=2022-11-01 |
There was a problem hiding this comment.
The api-version here should be 2023-01-01 instead of 2022-11-01 after bumping the api-version of Microsoft.ContainerService PR link: #25524
There was a problem hiding this comment.
@tyler-lloyd @FumingZhang Please help pull the latest code from remote dev branch, then please re-recording these failed tests test_aks_create_and_update_ipv6_count and test_aks_create_dualstack_with_default_network
|
We need the flag |

Related command
az aks createandaz aks updateDescription
This PR introduces the properties from aks-extensions that support the dual-stack feature.
Dual-stack is moving to GA and part of the work includes baking it into the GA cli to remove
the dependency on aks-preview extension.
Testing Guide
Unit and live tests added, mostly copied from the aks-preview extension work.
Example create:
Creates a dual-stack cluster with user-specified IP ranges
az aks create -n myCluster -g myRG --ip-families ipv4,ipv6 --pod-cidrs 10.244.0.0/16,fd12:3456:f::/64 --service-cidrs 192.168.0.0/16,fd00:abcd:ff::/108Example update:
Updates the current dual-stack cluster with 4 managed outbound IPv6 IPs
az aks update -n myCluster -g myRG --load-balanacer-managed-outbound-ipv6-count 4History Notes
[AKS]
az aks create: Add new parameter--pod-cidrsfor setting the IP ranges used to allocate IPs to pods[AKS]
az aks create: Add new parameter--service-cidrsfor setting the K8s service IPs[AKS]
az aks create: Add new parameter--ip-familiesfor setting the IP types that should be used in a cluster (IPv4 or IPv6)[AKS]
az aks create: Add new parameter--load-balanacer-managed-outbound-ipv6-countfor setting the number of IPv6 outbound IPs that AKS should managed for a cluster with IPv6 enabled[AKS]
az aks update: Support changing the load balancer managed outbound IPv6 count propertyThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.