cilium: rename aws/eni/routing to pkg/datapath/linux/routing#11452
cilium: rename aws/eni/routing to pkg/datapath/linux/routing#11452aanm merged 1 commit intocilium:masterfrom
Conversation
|
Please set the appropriate release note label. |
There was a problem hiding this comment.
Thanks for following up! A few small comments to address for me. Also #11328 is pending, but should be merged soon which I'd like to get in before this one.
There was a problem hiding this comment.
We should update this comment
There was a problem hiding this comment.
| // are setting the Src because interfacesingress rules don't have | |
| // are setting the Src because ingress rules don't have |
Nit
There was a problem hiding this comment.
| }).Debug("Deleting endpoint interface rules") | |
| }).Debug("Deleting endpoint routing rules") |
I like "routing" better here as "interface rules" isn't very informative
There was a problem hiding this comment.
| errs = append(errs, fmt.Errorf("unable to delete endpoint interface rules: %s", err)) | |
| errs = append(errs, fmt.Errorf("unable to delete endpoint routing rules: %s", err)) |
|
Added backport label as I'd like to backport this to 1.7 since it'll be a branch we support for a while and this PR has changed code which was recently backported, so it'll be good to keep the divergence to a minimum. |
53a7787 to
65fb484
Compare
|
Please set the appropriate release note label. |
|
This needs a rebase now that #11328 is merged. |
There was a problem hiding this comment.
Thanks for following up on this.
Per discussion in #11268 : the routing rules we use here are in
no way specific to AWS ENI; they are for also used to setup
Azure IPAM routes.
While at it, also garbage collect routes on endpoint deletion
when running Azure IPAM mode.
I was surprised that the PR named "rename ..." made functional changes, same with the commit naming. Please consider using the biggest change as the title for the PR and commit to make it more clear for anyone searching through the PRs or commits later.
In a similar vein, in future please consider splitting functional changes into a separate commit from the refactoring changes. If we end up wanting to trace back and git-bisect the tree, it's easier to understand what changed when commits are smaller and when the changes are incremental with either functional or cosmetic changes. As is, when I glance through git log, I would have a tendency to skip over this commit because it sounds like it doesn't make any functional changes. Commits like this break this assumption which can be painful when attempting to find the cause of an issue later on via git logs.
The changes themselves look fine. Given that you'll need to do a rebase anyway, do you mind fixing up the commit title?
65fb484 to
26c406a
Compare
|
@joestringer duly noted. I rebased and updated commit title as suggested. |
|
test-me-please |
|
retest-runtime |
|
retest-net-next |
Also garbage collect routes on endpoint deletion when running Azure IPAM mode (the same way we do on AWS instances). And rename aws/eni/routing to pkg/datapath/linux/routing: per discussion in cilium#11268 : the routing rules we use here are in no way specific to AWS ENI; they are for also used to setup Azure IPAM routes. Signed-off-by: Benjamin Pineau <benjamin.pineau@datadoghq.com>
26c406a to
f8f1f0d
Compare
|
test-me-please |
Due to the refactor from #11452, the device name was renamed from "enirouting-test" to "linuxrouting-test" which is 17 characters long, exceeding the max device name size (`IFNAMSIZ`) of 16. [1] This commit renames the device name to be under 16 characters. Fixes #11547 Fixes #11452 [1]: https://elixir.bootlin.com/linux/v5.6/source/include/uapi/linux/if.h#L33 Signed-off-by: Chris Tarazi <chris@isovalent.com>
Due to the refactor from #11452, the device name was renamed from "enirouting-test" to "linuxrouting-test" which is 17 characters long, exceeding the max device name size (`IFNAMSIZ`) of 16. [1] This commit renames the device name to be under 16 characters. Fixes #11547 Fixes #11452 [1]: https://elixir.bootlin.com/linux/v5.6/source/include/uapi/linux/if.h#L33 Signed-off-by: Chris Tarazi <chris@isovalent.com>
[ upstream commit 2141eca ] Due to the refactor from #11452, the device name was renamed from "enirouting-test" to "linuxrouting-test" which is 17 characters long, exceeding the max device name size (`IFNAMSIZ`) of 16. [1] This commit renames the device name to be under 16 characters. Fixes #11547 Fixes #11452 [1]: https://elixir.bootlin.com/linux/v5.6/source/include/uapi/linux/if.h#L33 Signed-off-by: Chris Tarazi <chris@isovalent.com> Signed-off-by: Jarno Rajahalme <jarno@covalent.io>
[ upstream commit 2141eca ] Due to the refactor from #11452, the device name was renamed from "enirouting-test" to "linuxrouting-test" which is 17 characters long, exceeding the max device name size (`IFNAMSIZ`) of 16. [1] This commit renames the device name to be under 16 characters. Fixes #11547 Fixes #11452 [1]: https://elixir.bootlin.com/linux/v5.6/source/include/uapi/linux/if.h#L33 Signed-off-by: Chris Tarazi <chris@isovalent.com> Signed-off-by: Jarno Rajahalme <jarno@covalent.io>
[ upstream commit 2141eca ] Due to the refactor from #11452, the device name was renamed from "enirouting-test" to "linuxrouting-test" which is 17 characters long, exceeding the max device name size (`IFNAMSIZ`) of 16. [1] This commit renames the device name to be under 16 characters. Fixes #11547 Fixes #11452 [1]: https://elixir.bootlin.com/linux/v5.6/source/include/uapi/linux/if.h#L33 Signed-off-by: Chris Tarazi <chris@isovalent.com> Signed-off-by: Jarno Rajahalme <jarno@covalent.io>
[ upstream commit 2141eca ] Due to the refactor from #11452, the device name was renamed from "enirouting-test" to "linuxrouting-test" which is 17 characters long, exceeding the max device name size (`IFNAMSIZ`) of 16. [1] This commit renames the device name to be under 16 characters. Fixes #11547 Fixes #11452 [1]: https://elixir.bootlin.com/linux/v5.6/source/include/uapi/linux/if.h#L33 Signed-off-by: Chris Tarazi <chris@isovalent.com> Signed-off-by: Jarno Rajahalme <jarno@covalent.io>
Per discussion in #11268 : the routing rules we use here are in
no way specific to AWS ENI; they are for also used to setup
Azure IPAM routes.
While at it, also garbage collect routes on endpoint deletion
when running Azure IPAM mode.
Signed-off-by: Benjamin Pineau benjamin.pineau@datadoghq.com