Skip to content

Load balancer's withExistingVMs should create a backend right away, not guess later #987

Description

@martinsawicki

right now, withExistingVMs assumes a default backend to be created as needed at creation time or associates the VMs with the first backend found on the LB. This was the initial tentative logic. The proper way to do this though, now that backend infrastructure is supported is for each withExistingVMs call to create a separate backend right away for that set of VMs and remove the guesswork at creation time.
This also means an overload for withExistingVMs is needed that optionally takes a name for the new backend.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions