You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@btzq , if we implement #8864 , the firewall functionality will be supported by virtue of the private IPs. The user facing functionality will be somewhat different but the security features will be the same. A user wanting to set access lists into a VPC will have to know about its topology anyway. What do you think?
@DaanHoogland when you mean topopology, do you mean that the users will need to know the existance of a the Virtual Router?
yes, but mostly the mapping of private IPs to static NAT Ips and individual services mapped from other IPs to the backends.
bad example:
public 10.10.10.10 - source NAT
public 10.10.10.11 - static NAT to private 10.11.12.10
public 10.10.10.12 - port 80 loadbalanced over 10.11.13.10 and 10.11.13.11
etc.
Hmm this is my opinion but i think part of the beauty of having cloud is that the customer does not need to know the topology of the underlying cloud service/infra. If the customer needs to learnt he existance of a router, it might complicate things for them and deter them from using the service.
Activity
DaanHoogland commentedon Apr 11, 2024
@btzq , if we implement #8864 , the firewall functionality will be supported by virtue of the private IPs. The user facing functionality will be somewhat different but the security features will be the same. A user wanting to set access lists into a VPC will have to know about its topology anyway. What do you think?
btzq commentedon Apr 12, 2024
@DaanHoogland when you mean topopology, do you mean that the users will need to know the existance of a the Virtual Router?
DaanHoogland commentedon Apr 12, 2024
yes, but mostly the mapping of private IPs to static NAT Ips and individual services mapped from other IPs to the backends.
bad example:
public 10.10.10.10 - source NAT
public 10.10.10.11 - static NAT to private 10.11.12.10
public 10.10.10.12 - port 80 loadbalanced over 10.11.13.10 and 10.11.13.11
etc.
btzq commentedon Apr 12, 2024
Hmm this is my opinion but i think part of the beauty of having cloud is that the customer does not need to know the topology of the underlying cloud service/infra. If the customer needs to learnt he existance of a router, it might complicate things for them and deter them from using the service.
[-]Support ACL on Public IP[/-][+]Support firewall rules on Public IP in VPC[/+]8 remaining items
OVN plugin: complete the auto-seeded OVN offerings for fresh installs
OVN plugin: complete the auto-seeded OVN offerings for fresh installs
OVN plugin: complete the auto-seeded OVN offerings for fresh installs