Update testing instructions to add a vnet
Creating something other than a resource group confirms that conversion
webhooks are working as well as the name -> azure name defaulting.
5. Source the SP credentials to use for the secret and then run `./scripts/deploy_testing_secret.sh sp`
6. Deploy the operator from MCR: `k apply --server-side=true -f <path-to-downloaded-yaml>` (We need to use [server-side apply](https://kubernetes.io/docs/reference/using-api/server-side-apply/) because the CRD for VirtualMachines is large enough that it can't fit in the `last-applied-configuration` annotation client-side `kubectl apply` uses.)
7. Wait for it to start: `k get all -n azureserviceoperator-system`
-8. Create a resource group: `k apply -f v2/config/samples/resources/v1alpha1api20200601_resourcegroup.yaml`
-9. Make sure it deploys successfully, and check in the portal.
+8. Create a resource group and a vnet in it (the vnet is to check that conversion webhooks are working, since there aren't any for RGs):
+ ```
+ k apply -f v2/config/samples/resources/v1alpha1api20200601_resourcegroup.yaml
+ k apply -f v2/config/samples/network/v1alpha1api20201101_virtualnetwork.yaml
+ ```
+9. Make sure they deploy successfully - check in the portal as well.
# Fixing an incorrect release
If there was an issue publishing a new release, we may want to delete the existing release and try again.
