You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking to have a single CRD definition for multiple virtual addresses, since cloud deployments could need multiple private addresses this would solve the need for two virtualservers deployed.
Description
I assumed reading the documentation that service_address would solve this, but looking into the schema this appears to just be an additional setting to the single virtual address. If this is actually possible, I have not been able to find an example on any F5 property.
Actual Problem
Maintaining two configuration files for one object is not a great way
Solution Proposed
AS3 accepts this as a string of addresses, that in turn become multiple virtual servers. CRD should be able to insert the same when crafting the as3 declaration
I thought maybe this class in CRD could do what I'm looking because the docs are worded that way. However, it only appears to just be an additional feature for the single address
Title
Looking to have a single CRD definition for multiple virtual addresses, since cloud deployments could need multiple private addresses this would solve the need for two virtualservers deployed.
Description
I assumed reading the documentation that service_address would solve this, but looking into the schema this appears to just be an additional setting to the single virtual address. If this is actually possible, I have not been able to find an example on any F5 property.
Actual Problem
Maintaining two configuration files for one object is not a great way
Solution Proposed
AS3 accepts this as a string of addresses, that in turn become multiple virtual servers. CRD should be able to insert the same when crafting the as3 declaration
Something like:
Alternatives
Creating multiple CRD resources
Additional context
I thought maybe this class in CRD could do what I'm looking because the docs are worded that way. However, it only appears to just be an additional feature for the single address
https://clouddocs.f5.com/containers/latest/userguide/crd/virtualserver.html?highlight=serviceaddress
The text was updated successfully, but these errors were encountered: