Azure provider does not support "Standard" SKU floating IPs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Christopher Lee | ||
2.3 |
Won't Fix
|
High
|
Unassigned | ||
2.4 |
Fix Released
|
High
|
Christopher Lee |
Bug Description
Juju provisioned azure VMs use "Basic" SKU floating IPs [0] and I can't see any way to change this
What it means is that juju deployed VMs can't be used with "Standard" load balancers which they recommend for all new deployments [1].
This is very limiting. It means that load balancers used by juju services can't be monitored easily as "Basic" load balancers only offer limited visibility.
There is also no safe way to migrate manually that I can think of. Changing floating IPs from underneath juju sounds risky. Also any "juju add-unit" commands would end up using "Basic" SKU so I'd have mix of SKUs.
Could juju either migrate to "Standard" SKU or provide option to change it?
[0] https:/
[1] https:/
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 2.5-beta1 |
Changed in juju: | |
milestone: | 2.5-beta1 → 2.5-beta2 |
Changed in juju: | |
assignee: | nobody → Christopher Lee (veebers) |
Changed in juju: | |
status: | Triaged → Fix Committed |
Changed in juju: | |
milestone: | 2.5-beta2 → 2.5-beta3 |
Changed in juju: | |
status: | Fix Committed → Fix Released |