azure: support multiple pods subnets#11268
Merged
tgraf merged 1 commit intocilium:masterfrom May 6, 2020
Merged
Conversation
|
Please set the appropriate release note label. |
Member
|
test-me-please |
Member
|
test-me-please |
ungureanuvladvictor
requested changes
May 1, 2020
945a51f to
f9a4d97
Compare
Member
|
test-me-please |
ungureanuvladvictor
approved these changes
May 2, 2020
tgraf
suggested changes
May 4, 2020
Contributor
There was a problem hiding this comment.
Please rename this function if we don't exclusively use it for ENI.
Contributor
Author
There was a problem hiding this comment.
Done.
Relatedly, most of that function meat recently moved to pkg/aws/eni/routing package, which is in no way specific to AWS.
Mind if I rename that to, say, pkg/nic/routing for instance (or another name suggestion @tgraf )?
And while at it, also hook in the newly introduced routes deletion on endpoint removal - perhaps material for a follow up PR?
Contributor
There was a problem hiding this comment.
@bpineau Good point. I think it should be moved into pkg/datapath/linux/routing.
Support pods attached to secondary interfaces and spread over several subnets: inject explicit routes and rules to forward pods traffic to their subnet gateway and back, set MTU, etc. the same way Cilium does for AWS/ENI. We mostly need to propagate subnets gw details (collecting addressPrefix from instances manager so we can infer the subnets gateways addresses) down to API / CRD, which can then be leveraged by the CNI plugin as we do with ENIs. While at it, also support k8s clusters and vpc/subnets running on different resource groups. Signed-off-by: Benjamin Pineau <benjamin.pineau@datadoghq.com>
f9a4d97 to
b8c9023
Compare
Member
|
test-me-please |
tgraf
approved these changes
May 6, 2020
bpineau
added a commit
to DataDog/cilium
that referenced
this pull request
May 14, 2020
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>
aanm
pushed a commit
that referenced
this pull request
May 15, 2020
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 #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>
jrajahalme
pushed a commit
that referenced
this pull request
May 20, 2020
[ upstream commit fac1802 ] 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 #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> Signed-off-by: Jarno Rajahalme <jarno@covalent.io>
aanm
pushed a commit
that referenced
this pull request
May 25, 2020
[ upstream commit fac1802 ] 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 #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> Signed-off-by: Jarno Rajahalme <jarno@covalent.io>
jrajahalme
pushed a commit
that referenced
this pull request
May 28, 2020
[ upstream commit fac1802 ] 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 #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> Signed-off-by: Jarno Rajahalme <jarno@covalent.io>
christarazi
pushed a commit
that referenced
this pull request
May 28, 2020
[ upstream commit fac1802 ] 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 #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> Signed-off-by: Jarno Rajahalme <jarno@covalent.io>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Support pods attached to secondary interfaces, and spread over several
subnets: inject explicit routes and rules to forward pods traffic to
their subnet gateway band back, set MTU, etc. the same way Cilium does
for AWS/ENI.
We mostly need to propagate subnets gw details (collecting addressPrefix
from instances manager so we can infer the subnets gateways addresses)
down to API / CRD, which can then be leveraged by the CNI plugin as we
do with ENIs.
While at it, also support k8s clusters and vpc/subnets running on
different resource groups.
Signed-off-by: Benjamin Pineau benjamin.pineau@datadoghq.com