This resource is namespace scoped, refer to [Namespace](./namespace.md) for details.

Note: Network deletion progress will wait all the dependents being deleted first before proceeding to the actual delete actions. That is, the Network deletion will be pended if there are any dependents running in the Network.

Example:

```bash
# delete the Network and all resources in the Network
> kubectl delete network aws-us-west-2
# the order does not matter, Network controller will wait for the cluster to be deleted before deleting the underlying Network resources
> kubectl delete cluster 123
```

Bad example:

```bash
# only delete the Network, the deletion will be pended forever since there are other resources running in this Network
> kubectl delete network aws-us-west-2
```

You may use `OwnerReference` to instruct Infra API to delete the dependents automatically when deleting a Network, but it is not recommended
to set OwnerReference between Network and Cluster since the cluster deletion should be controlled with care.