Warning: very new beginner! Pls forgive me if I'm asking a very silly question.
As per training course, as I understand that a default network should be provisioned with a new project.
The words from cloudskillsboost
Many users get started with GCP is to define their own Virtual Private Cloud inside
their first GCP project. Or they can simply choose the default VPC and get started
with that.
But there's no network defined in my new provisioned project, so when I create new VM instance or launch compute engine from marketplace, I'm complained with no network problem. I'm wrong?
I did a search inside this community but no luck, I'm also very new to this community lol~
Solved! Go to Solution.
Hi!
Great question, so the answer is you're not wrong, but as always there might be an exception.
Out of the box, new projects do come with a 'default' VPC configured in 'auto' mode, this is a great way to get going quickly, see: https://cloud.google.com/vpc/docs/vpc#default-network
However, as it says on that link, you can disable this, with an organisational policy constraint, "compute.skipDefaultNetworkCreation", see: https://cloud.google.com/vpc/docs/vpc#org-policies
So perhaps in your case there is an org policy that has disabled this?
I would say that while the default network is great to get going quickly and for testing, good practice is always to be more specific about your networking, creating custom defined networks for your workloads. That way you're always in full control over what addressing is in use and what is provisioned, which is why many organisations choose to use this policy.
Hope that helps, all the best,
Alex
Hi!
Great question, so the answer is you're not wrong, but as always there might be an exception.
Out of the box, new projects do come with a 'default' VPC configured in 'auto' mode, this is a great way to get going quickly, see: https://cloud.google.com/vpc/docs/vpc#default-network
However, as it says on that link, you can disable this, with an organisational policy constraint, "compute.skipDefaultNetworkCreation", see: https://cloud.google.com/vpc/docs/vpc#org-policies
So perhaps in your case there is an org policy that has disabled this?
I would say that while the default network is great to get going quickly and for testing, good practice is always to be more specific about your networking, creating custom defined networks for your workloads. That way you're always in full control over what addressing is in use and what is provisioned, which is why many organisations choose to use this policy.
Hope that helps, all the best,
Alex
A great answer explains all why where how, I can check the organizational policy with our administrator