Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFE: Support for Route-Domain override in F5 IPAM-integrated CR #3418

Open
adityoari opened this issue May 15, 2024 · 3 comments
Open

RFE: Support for Route-Domain override in F5 IPAM-integrated CR #3418

adityoari opened this issue May 15, 2024 · 3 comments

Comments

@adityoari
Copy link

Title

Support for Route-Domain override in F5 IPAM-integrated CR

Description

Enhance F5 CRs (VirtualServers, TransporServer) to expose and accept explicit Route-Domain ID

Actual Problem

Customer needs to override the default partition RD for the VS created by CIS due to network constraints.
With explicit addressing, they can append the %RD into virtualServerAddresses parameter value.
However, with F5 IPAM Controller integration using the ipamLabel parameter, there's no way to configure the %RD suffix.
Trying to manually append the %RD in the IPAM spec triggers validation error, and I don't suppose external IPAM providers even understands the %RD notation.

Solution Proposed

Expose, accept, and implement new parameter (e.g. ipamRD) in the CR spec to provide Route-Domain ID to be appended to the resulting AS3 declaration.
Sample:

spec:
  virtualServerName: "vs1"
  ipamLabel: Prod
  ipamRD: 10
  virtualServerPort: 80

Alternatives

An alternative would be to expose similar parameter in the containers.args of f5-ipam-controller, but this might completely change the format of the IP address returned by IPAM to CIS, resulting in changes in both IPAM & CIS.
Sample:

containers:
- args:
  - --orchestration=kubernetes
  - --ip-range='{"Dev":"10.0.0.40-10.0.0.49", "Prod":"10.0.0.100-10.0.0.109"}'
  - --route-domain=10

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.
See Issue #3416

@trinaths
Copy link
Contributor

@adityoari is #3416 not duplicate of this issue ?

@adityoari
Copy link
Author

@trinaths the symptoms & original scenarios were not actually the same, but I can see how the team might have a combined solution to solve both.

To reiterate, customer requires support of route-domain override:

  1. as new IPAM-specific spec (ipamRD in the example above) of VirtualServer & TransportServer CRs
  2. as %RD suffix in the spec.virtualServerAddress of IngressLink CR

@trinaths
Copy link
Contributor

Created [CONTCNTR-4746] for internal tracking.

@trinaths trinaths added JIRA and removed untriaged no JIRA created labels May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants