This message was deleted.
# neuvector-security
a
This message was deleted.
q
Yes. Create a group that defines it, then add a network rule to the top that allows
p
so would the group be something like network=0.0.0.0/0? i cant tell if that would include container to container traffic as well or only external/node
q
the group would be that netblock, like…
then I’m pretty sure you’d want a rule for both directions
but, obviously, test it. 🙂
p
so what if we wanted a pod to be able to connect to -any- internal or external traffic though, would i need two rules outbound, one for the 'containers' group and one for the 'external' group? something similar to a cisco firewalls 'permit 10.1.1.1 any any'
q
‘external’ is a group that generally represents anything outside the cluster
so, from
containers
to
allow group
for outbound and then reverse it
you might need to dupe for nodes, as well 🤔
p
gotcha, so one for each of the primary groups that were generated, there isnt a way to make a group of groups i suppose 😅
q
i wish
😄