Comment 2 for bug 1964563

Yep, you are right, but I want to replenish some details yet:
Kuryr should support that the below annotations:
openstack.org/kuryr-subnet-pool
  used to auto create pod subnet, if not specified means user want to use the communal subnet pool(configured by pod_subnet_pool).
openstack.org/kuryr-subnet
  if not specified, kuryr will auto create a subnet for the namespace
openstack.org/kuryr-router
  support three types value: router id, auto, ""
  if the value is auto, the kuryr will auto create a router for the namespace
  if the value is "", kuryr will do not connect the pod subnet to router
  if the namespace has no the annotation, means user want to connect the pod subnet to the communal router.
openstack.org/kuryr-project
  For details: https://review.opendev.org/c/openstack/kuryr-kubernetes/+/832768

For Network Policies, I don't test it yet. But, I think that a independent tenant will expect a independent IPAM (The cidr will not be affected by other tenant). In my opinion, only use Network Policy can not meet this require.