Enable Route-Domain suffix %rd in virtualServerAddress of IngressLink CR

[adityoari]

Title

Enable Route-Domain suffix %rd in virtualServerAddress of IngressLink CR

Description

Enhance IngressLink to accept %rd suffix in spec.virtualServerAddress

Actual Problem

Deploying IngressLink CR to CIS v2.16.1 having the virtualServerAddress value in the format of ip%rd immediately rejected by the API with the following error.

The IngressLink "ingresslink1" is invalid: spec.virtualServerAddress: Invalid value: "10.0.0.136%10": spec.virtualServerAddress in body should match '^(([0-9]|[1-9][0-9]|1[0-9]{2}|2[0-4][0-9]|25[0-5])\.){3}([0-9]|[1-9][0-9]|1[0-9]{2}|2[0-4][0-9]|25[0-5])$'

Seems like the parameter validator/parser only accept raw IPv4 octets and doesn't even consider any %RD notation.

Solution Proposed

Enhance the IngressLink CR to correctly identify, parse, and apply the %RD notation, just like VirtualServer or TransportServer CRs.

Alternatives

Expose the RD as separate parameter, e.g. spec.virtualServerRD
This would be inconsistent with other CRs so please only consider this as the last option.

Additional context

Due to network environment constraints, customer requires VS to be in the different RD than the partition default RD used by the Pool Members.

[adityoari]

Closing this issue and merging the use-case to issue #3418