Comments (15)
Related to Azure/azure-powershell#2042
from bosh-azure-cpi-release.
@svrc-pivotal It is a good idea. Let us do some investigation.
from bosh-azure-cpi-release.
@svrc-pivotal Now Azure has supported to create one external LB and one internal LB in the same NIC. Could you have a try?
from bosh-azure-cpi-release.
@svrc-pivotal Need to correct. Azure can support to create create one external LB and one internal LB in the same NIC but the port rules cannot be same. We are still investigating.
from bosh-azure-cpi-release.
There is a question and answer at this link about multiple load balancers, saying that:
- Azure NICs can participate in multiple load-balancer: one external and one internal.
- LB rules on the external and internal load-balancers cannot use the same backend port.
- Only the primary NIC can be used in load-balancer backend pools.
I had tried to create rule tcp 22:22 for both external and internal load balancers and assigned those two lbs to the same VM, I got error code "RulesUseSameBackendPortProtocolAndIPConfig" when creating the VM.
Hi @svrc-pivotal, are you expecting to use same backend port in load balancers in CF? Azure does not support such feature now.
from bosh-azure-cpi-release.
Hi @gossion yeah the idea was that I could reduce the number of HA proxy instances.. they would use the same backend port. I guess we'll have to wait to see if Azure improves LBs to enable the same backend ports.
from bosh-azure-cpi-release.
Hi @svrc-pivotal ,
Now in Azure the secondary NICs can also be used in LB backend pools, so this feature is doable. However, the secondary NICs can't be probed by LB because by default the outbound traffic will go to gateway of primary NIC. In order to make LB work with the secondary NICs we need to configure a policy route in the VM, which means we need a bosh release to configure the network additionally. I had a PR in networking-release, trying to implement the policy routing for this scenario, but it is not reviewed / merged yet.
It looks like this is not a common scenario, and the issue has last for a long time. Not sure if you have already solved the issue by any other methods, so my question is - do you still need this feature?
from bosh-azure-cpi-release.
@gossion At the moment we deploy separate VMs if we need separate load balancers. I have at least two large Azure customers deploying separate VMs for internal vs. external facing HAproxies for example.
I guess my point was that Azure is the only cloud I know (out of AWS, OpenStack, GCP, vSphere) that requires multiple NICs for multiple load balancers, so this should be a common case. Multi-NIC could be a workaround but seems too early.
We can close this issue if it doesn't look like Azure LBs will ever allow a single NIC to expose to multiple load balancers, as it's a larger concern than just this CPI :)
from bosh-azure-cpi-release.
This should work with standard
LB skus and maybe should be revisited, especially considering SNAT with standard
LBs requires a public LB with unused inbound rules to denote SNAT outbound IPs/ports (scenario 2 here - https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-outbound-connections ).
I could forsee a case where if using standard
LBs that every VM in a BOSH deployment gets a public LB assigned for outbound SNAT purposes, and then a subset of VMs require a second LBs for internal purposes. (Or is is preferred to mix internal/external frontends on the same LB in a standard
case? admittedly I don't know)
from bosh-azure-cpi-release.
Any updates regarding supporting multiple LBs attached to the same VM orchestrating via BOSH? We currently are accomplishing this using a separate piece of automation to attach the VMs after deployment to the second LB (one internal, one external), however it would be nice to simplify and eliminate the need for out of band changes.
from bosh-azure-cpi-release.
This issue was marked as Stale
because it has been open for 21 days without any activity. If no activity takes place in the coming 7 days it will automatically be close. To prevent this from happening remove the Stale
label or comment below.
from bosh-azure-cpi-release.
Not stale - waiting on updates from the BOSH team.
from bosh-azure-cpi-release.
This issue was marked as Stale
because it has been open for 21 days without any activity. If no activity takes place in the coming 7 days it will automatically be close. To prevent this from happening remove the Stale
label or comment below.
from bosh-azure-cpi-release.
This issue was closed because it has been labeled Stale
for 7 days without subsequent activity. Feel free to re-open this issue at any time by commenting below.
from bosh-azure-cpi-release.
this issue should be fixed with PR #638 which was released with v37.6.0.
from bosh-azure-cpi-release.
Related Issues (20)
- Support Ephemeral OS Disks HOT 2
- Allow For Custom Disk Size When Specifying use_root_disk = true HOT 2
- CPI v37.3.1 failes to delete stemcells HOT 2
- Permissions issue if more then one user doing deployments HOT 7
- Azure CPI needs a new ways to deploy VMs HOT 6
- Support for application gateways with multiple backend pools HOT 9
- BOSH Azure CPI could provide API to automatically add diego cell or Create VM on which containers can be deployed on . #4 HOT 1
- development.md env setup is broken: vendor_gems script fails with gem not found error HOT 4
- Rubocop dev dependencies/scripts are broken
- Increase unit test coverage to 100% HOT 2
- Reduce ignored rubocop offenses HOT 4
- New BOSH Azure CPI release HOT 5
- Bosh director self snapshots are not being triggered HOT 4
- Improve JSON parsing speed by using Oj or FastJsonParser HOT 6
- Azure IMDS endpoint calls do not work when multiple UserAssigned managed identities are available HOT 3
- Azure ephemeral OS/temp disk HOT 7
- Support the azure blobstore as external blobstore for bosh HOT 12
- Local tests are not working on Linux (WSL2) HOT 4
- VM is being created with MS DNS even when local_dns is specified. HOT 6
- CVE-2024-27280 HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from bosh-azure-cpi-release.