-
Notifications
You must be signed in to change notification settings - Fork 209
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
tests: egressgw: minor improvements and clean ups #2063
Conversation
d187988
to
d5e1cb1
Compare
d5e1cb1
to
3c8b316
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not this PR to blame, still I found it a bit confusing that EgressGatewayPolicy's excludedCIDRs
looks like a field accepting a CIDR but instead accepting 0 or 1. Thanks!
to better document how the ExcludedCIDRs param of CiliumEgressGatewayPolicyParams works Signed-off-by: Gilberto Bertin <[email protected]>
add a new PodSelectorKind parameter to CiliumEgressGatewayPolicyParams, which allows to select the pod matching the "kind" label Signed-off-by: Gilberto Bertin <[email protected]>
As CiliumEgressGatewayPolicyParams allows now to use a single policy template across all test scenarios, stop passing the same policy template to all invocations of WithCiliumEgressPolicy() Signed-off-by: Gilberto Bertin <[email protected]>
and make it available to hooks Signed-off-by: Gilberto Bertin <[email protected]>
3c8b316
to
162da0a
Compare
yeah that's fair 👍 perhaps I can rename it to |
rename the ExcludedCIDRs CiliumEgressGatewayPolicyParams field to ExcludedCIDRsConf to make it more explicit its use case Signed-off-by: Gilberto Bertin <[email protected]>
see individual commits