Compute node may use one external network IP (more simple case) or existing provider network IP but different routing rules will be required in both cases.
I propose that 'disable-snat' will be a limiting setting for 'Local SNAT' as well. If cloud admin set 'disable-snat' for some router - SNAT traffic should be disabled in all computer nodes for all relevant internal networks this router is connected to.
As a side note: 'Local SNAT' mode could use either manual setting for chosen compute node/s and have a client API for this. Or use automatic mode (detect external network) with configuration enabled option.
Compute node may use one external network IP (more simple case) or existing provider network IP but different routing rules will be required in both cases.
I propose that 'disable-snat' will be a limiting setting for 'Local SNAT' as well. If cloud admin set 'disable-snat' for some router - SNAT traffic should be disabled in all computer nodes for all relevant internal networks this router is connected to.
As a side note: 'Local SNAT' mode could use either manual setting for chosen compute node/s and have a client API for this. Or use automatic mode (detect external network) with configuration enabled option.