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

Breaking changes of Network API version 2020-08-01 #403

Closed
feiskyer opened this issue Sep 30, 2020 · 5 comments · Fixed by #569
Closed

Breaking changes of Network API version 2020-08-01 #403

feiskyer opened this issue Sep 30, 2020 · 5 comments · Fixed by #569
Assignees
Milestone

Comments

@feiskyer
Copy link
Member

Refer https://azure.microsoft.com/en-us/updates/zone-behavior-change/:

With Network API version 2020-08-01, zone behavior for Standard SKU resources (Azure Load Balancer and Public IP addresses) will be updated such that:

  • when no zone is specified, a non-zonal resource is created
  • when a single zone is specified, a zonal resource is created
  • when multiple zones are specified in a region with Availability Zones, a zone-redundant resource is created

A zone-redundant resource can only be created in regions where Availability Zones are supported.

Previously, when no zone was specified, a zone-redundant resource was created. No changes will be made to existing Public IP or Standard Load Balancer resources with previous API versions.

We need to check how to ensure the expected AZ (e.g. from aks-engine and AKS) are set on SLB/PIP when upgrading network API version to 2020-08-01.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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 29, 2020
@feiskyer feiskyer removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 31, 2020
@feiskyer
Copy link
Member Author

feiskyer commented Mar 9, 2021

For checking whether a region supports the availability zone or not, provider LIST API (https://docs.microsoft.com/en-us/rest/api/resources/providers/list) could be used. Here is an example:

# query the zone mappings for virtualMachines
GET /subscriptions/<subscription-id>/providers?api-version=2020-06-01 | \
        jq '.value[] | select (.id == "/subscriptions/<subscription-id>/providers/Microsoft.Compute")' | \
        jq '.resourceTypes[] | select(.resourceType=="virtualMachines")' | \
        jq '.zoneMappings'
[
  {
    "location": "East US 2",
    "zones": [
      "2",
      "1",
      "3"
    ]
  },
  {
    "location": "Central US",
    "zones": [
      "2",
      "1",
      "3"
    ]
  },
  {
    "location": "West Europe",
    "zones": [
      "2",
      "1",
      "3"
    ]
  },
  {
    "location": "East US 2 EUAP",
    "zones": [
      "2",
      "1",
      "3"
    ]
  },
  {
    "location": "Central US EUAP",
    "zones": [
      "1",
      "2"
    ]
  },
  {
    "location": "France Central",
    "zones": [
      "2",
      "1",
      "3"
    ]
  },
  {
    "location": "Southeast Asia",
    "zones": [
      "2",
      "1",
      "3"
    ]
  },
  {
    "location": "West US 2",
    "zones": [
      "2",
      "1",
      "3"
    ]
  },
  {
    "location": "North Europe",
    "zones": [
      "2",
      "1",
      "3"
    ]
  },
  {
    "location": "East US",
    "zones": [
      "2",
      "1",
      "3"
    ]
  },
  {
    "location": "UK South",
    "zones": [
      "2",
      "1",
      "3"
    ]
  },
  {
    "location": "Japan East",
    "zones": [
      "2",
      "1",
      "3"
    ]
  },
  {
    "location": "Australia East",
    "zones": [
      "2",
      "1",
      "3"
    ]
  },
  {
    "location": "South Africa North",
    "zones": []
  },
  {
    "location": "South Central US",
    "zones": [
      "2",
      "1",
      "3"
    ]
  },
  {
    "location": "Canada Central",
    "zones": [
      "2",
      "1",
      "3"
    ]
  },
  {
    "location": "Germany West Central",
    "zones": [
      "2",
      "1",
      "3"
    ]
  },
  {
    "location": "Brazil South",
    "zones": [
      "2",
      "1",
      "3"
    ]
  },
  {
    "location": "Central India",
    "zones": []
  },
  {
    "location": "Korea Central",
    "zones": []
  }
]

@feiskyer
Copy link
Member Author

feiskyer commented Mar 9, 2021

/milestone v1.21

@k8s-ci-robot k8s-ci-robot added this to the v1.21 milestone Mar 9, 2021
@feiskyer feiskyer assigned feiskyer and nilo19 and unassigned feiskyer Mar 10, 2021
@feiskyer
Copy link
Member Author

Let's confirm whether the API version is available in all regions before working on the task.

@feiskyer
Copy link
Member Author

Confirmed 2020-08-01 API is available in all regions. @nilo19 we could start this work now.

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.

4 participants