fix: support mulltiple subnet when creating private endpoints #2065
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.
What type of PR is this?
/kind bug
What this PR does / why we need it:
fix: support mulltiple subnet when creating private endpoints
when specifying "networkEndpointType: privateEndpoint" in storage class, only first subnet is associated with a new private endpoint, this does not work when there are multiple subnets. Ideally when there are multiple subnets, multiple private endpoints should be created, every private endpoint is associated with one subnet, and only one dns zone will be created mapping to vnet and multiple private endpoints
For example, in csi logs below, there are two subnets(aks-subnet, subnet2), two private endpoint(f0240127bc91d4905903342-pvtendpoint-0, f0240127bc91d4905903342-pvtendpoint-1) will be created and one private DNS zone group(f0240127bc91d4905903342-dnszonegroup) will be created.
cloud-provider-azure pr: kubernetes-sigs/cloud-provider-azure#6783
csi logs:
Which issue(s) this PR fixes:
Fixes ##2047
Requirements:
Special notes for your reviewer:
Release note: