You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following the steps of creating the VPC, gcloud compute networks create kubernetes-the-hard-way --subnet-mode custom
and then creating a subnet, gcloud compute networks subnets create kubernetes \ --network kubernetes-the-hard-way \ --range 10.240.0.0/24
the step to create internal firewall rules (below) fails because there is another subnet in the source ranges: gcloud compute firewall-rules create kubernetes-the-hard-way-allow-internal \ --allow tcp,udp,icmp \ --network kubernetes-the-hard-way \ --source-ranges 10.240.0.0/24,10.200.0.0/16
The command above fails with the following message: ERROR: (gcloud.compute.firewall-rules.create) unrecognized arguments: 10.200.0.0/16] To search the help text of gcloud commands, run: gcloud help -- SEARCH_TERMS
Didn't see any other mention of the 10.200.0.0/16 subnet before this point. Not sure if I missed something.
The text was updated successfully, but these errors were encountered:
Hi,
Beginner here following the guide Provisioning Compute Resources
Following the steps of creating the VPC,
gcloud compute networks create kubernetes-the-hard-way --subnet-mode custom
and then creating a subnet,
gcloud compute networks subnets create kubernetes \ --network kubernetes-the-hard-way \ --range 10.240.0.0/24
the step to create internal firewall rules (below) fails because there is another subnet in the source ranges:
gcloud compute firewall-rules create kubernetes-the-hard-way-allow-internal \ --allow tcp,udp,icmp \ --network kubernetes-the-hard-way \ --source-ranges 10.240.0.0/24,10.200.0.0/16
The command above fails with the following message:
ERROR: (gcloud.compute.firewall-rules.create) unrecognized arguments: 10.200.0.0/16] To search the help text of gcloud commands, run: gcloud help -- SEARCH_TERMS
Didn't see any other mention of the 10.200.0.0/16 subnet before this point. Not sure if I missed something.
The text was updated successfully, but these errors were encountered: