SDN connectors and VDOMs

[bascheew]

When using VDOMs, SDN connectors are not available to be created at the VDOM level, only the global level.  Can a connector configured at global can be scoped down to a specific VDOM?  As I see it, any tenant on the Fortigate can create dynamic addresses by sourcing the global connector which means that IP address info is leaked to VDOMS that are not authorized to read that information.  Thoughts?

[plink013]

Be great if someone could provide some feedback on the above. As of 2022 this may be an issue for us as well. Any feedback is greatly appreciated.

[AndersV]

Hi, I would like to hear about this as well. Only able to create connection from global. Will this be supported in VDOM in the future?

[huonwu1]

The only possible limitations I know of with large units used to be complexity of spreading load between various NP units and having to be careful about what ports you use. All the new big units just have an ISF so all ports link back in to all NP, issue resolved https://mobdro.bio/ .

[AndersV]

huonwu1: not sure I understand how this is related to this thread. The problem is that kubernetes (and other sdn connectors) is not available under security fabric > external connectors inside a VDOM.