kernel NSC with multiple NetworkServices

[or-adar]

my knowledge is very limited, so I would like to know if I should use other approach that can suit my use case.

I have a pod in my cluster running NSC as a container,
I want it to connect to a large number of Network Services, so I'm expected to have multiple kernel interfaces injected to my pod's network namespace and multiple routing tables as well,
since in kernel mechanism, a routing table is expected to be injected for each connection ID (and NSC generates connection ID for each NS it wants to connect to).

Now, AFAIK, the linux kernel supports up to 252 additional routing tables. so it looks like I'm limited here to the number of possible Network Services I am allowed to Request.
Should I not use kernel mechanism? is there other alternatives or approaches to what I'm trying to acheive?

[glazychev-art]

@or-adar
This is a good question. Now we add routes to all NetworkServices in only one main table.

Let's say we have a new chain element that adds each new route to a separate routing table.
I'm not sure, but if we take a look at the iproute2 manual https://man7.org/linux/man-pages/man8/ip-route.8.html:

Route tables: Linux-2.x can pack routes into several routing
       tables identified by a number in the range from 1 to 2^32-1 ...

Am I missing something?

[or-adar]

@glazychev-art you're right. I think I got confused with older linux kernels
(as documented here: http://linux-ip.net/html/routing-tables.html) where the max was 255.

so it seems like it got increased for newer linux kernels,
which unlike what I first assumed, should not be a problem.
sorry, and thanks for the reference!

[glazychev-art]

@or-adar
Always happy to help!
Can we close the issue?

[or-adar]

sure!