search

Azure / azure-rest-api-specs

The source for REST API specifications for Microsoft Azure.
MIT License
2.62k stars 5.04k forks source link

Load Balancer Backend Address Pool (2020-05-01): only the designated endpoint is able to manipulate `loadBalancerBackendAddresses` #11234

Open magodo opened 3 years ago

magodo commented 3 years ago

The loadBalancerBackendAddresses applies to Standard sku of LB only.

However, if I created a Standard sku LB and try to manipulate it using the load balancer endpoint, it will take no effect.

On the other hand, it works if I send API against the load balancer backend address pool endpoint instead.

This is unnecessarily complicated from the users' perspective. Because now I have to tell whether the LB of the BAP is standard sku, if so then I can use the load balancer backend address pool endpoint, otherwise I will have to use the load balancer endpoint.

The expected behavior is:

ghost commented 3 years ago

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @slbsupportgithub.

slbsupportgithub commented 3 years ago

@Erichmailto:Erich.RobinsonTillenburg@microsoft.com to help

-a

From: msftbot[bot] notifications@github.com Sent: Friday, October 16, 2020 2:17 AM To: Azure/azure-rest-api-specs azure-rest-api-specs@noreply.github.com Cc: SLB Supportability GitHub Contacts slbsupportgithub@microsoft.com; Mention mention@noreply.github.com Subject: Re: [Azure/azure-rest-api-specs] Load Balancer Backend Address Pool (2020-05-01): only the designated endpoint is able to manipulate loadBalancerBackendAddresses (#11234)

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @slbsupportgithubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fslbsupportgithub&data=04%7C01%7Canavin%40microsoft.com%7C52dfbd15707e478ae12708d871b446bb%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637384366382622489%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=VZY0Ni4UH3roVDQLYCdBjOLclusintyHLbwfy5hPTPk%3D&reserved=0.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-rest-api-specs%2Fissues%2F11234%23issuecomment-709930330&data=04%7C01%7Canavin%40microsoft.com%7C52dfbd15707e478ae12708d871b446bb%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637384366382632447%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=SklMbFcVp%2BeEmmkRCwchrk%2FyG0aKfkzEWsUMhRqT3kI%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAOC5MPDITOQABPBY4LAFVFDSLAFRZANCNFSM4SS6JXYQ&data=04%7C01%7Canavin%40microsoft.com%7C52dfbd15707e478ae12708d871b446bb%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637384366382632447%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=xl0V8zxYUaRK0YZla2IU2MfwXAUjC%2F4Fd1ivMPh%2ByT0%3D&reserved=0.

anavinahar commented 3 years ago

We will not be able to support this for Basic SKU Load Balancers. Please follow docs: https://docs.microsoft.com/en-us/azure/load-balancer/backend-pool-management

and see limitations: https://docs.microsoft.com/en-us/azure/load-balancer/backend-pool-management#configure-backend-pool-by-ip-address-and-virtual-network

please-close.

magodo commented 3 years ago

How about:

allow the load balancer endpoint to be able to support the loadBalancerBackendAddresses

Since it makes no sense that the standard sku can't work with the load balancer endpoint. There is no where in the document or swagger mentioning this.

magodo commented 3 years ago

@anavinahar I'm afraid the document you provided above doesn't fully apply to LB of basic SKU.

Let me summarize the bahavior of BAP CRUD for different LB skus below:

LB Basic SKU

Operation Inline with LB towards LB endpoint Dedicated BAP endpoint
Create OK NOK (error, refused)
Read OK OK
Delete OK NOK (error, refused)

LB Standard SKU

Operation Inline with LB towards LB endpoint Dedicated BAP endpoint
Create OK OK
Update NOK (no effect) OK
Read OK OK
Delete NOK (no effect) OK

From the observation above, I assume that users should use the LB endpoint to manipulate BAP when its sku is basic, and use the dedicated BAP endpoint when its sku is standard?

I wonder if there is any document mentioning this?