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
Is your feature request related to a problem? Please describe.
We need for each ingress separate IP from IPAM (Range) for each ingress similar like LB type behaviour.
This would help us to configure the firewall policies in a much more accurate way.
Describe the solution you'd like
We need for each ingress separate IP from IPAM (Range) for each ingress.
The controller then should select an IP from a specified IPAM Range.
Describe alternatives you've considered
none
Additional context
We had already a chat conversation through the google chat channel "Hansemerkur" with Mayur Mohan Patil. He asked us to raise an enhancement request.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
We need for each ingress separate IP from IPAM (Range) for each ingress similar like LB type behaviour.
This would help us to configure the firewall policies in a much more accurate way.
Describe the solution you'd like
We need for each ingress separate IP from IPAM (Range) for each ingress.
The controller then should select an IP from a specified IPAM Range.
Describe alternatives you've considered
none
Additional context
We had already a chat conversation through the google chat channel "Hansemerkur" with Mayur Mohan Patil. He asked us to raise an enhancement request.
The text was updated successfully, but these errors were encountered: