googleapi: Error 400: Cluster CIDR range is not within allowed ranges., badRequest

[yardenas]

Hi,

We're trying to deploy an airflow cluster with this blueprint, using a shared VPC.

We created a subnet as specified in your fast network peering stage.

Also, I'm specifying the following configuration:

    composer_secondary_ranges = {
      pods     = "pods"
      services = "services"
    }

Unfortunately, I'm getting this error:

googleapi: Error 400: Cluster CIDR range 100.128.48.0/20 is not within allowed ranges., badRequest

I'm not entirely sure how to proceed. Any suggestions?

[juliocc]

My only guess is that you have to use an RFC1918 range. Can you try that?

@lcaggio any ideas?

[yardenas]

Yes, you're right, this IP doesn't conform with RFC1918. Thing is, we got this IP from fast

[yardenas]

We changed this file to the following:

# skip boilerplate check

region: us-central1
description: Default subnet for dev Data Platform
ip_cidr_range: 172.16.0.0/12
secondary_ip_ranges:
  pods: 10.10.8.0/22
  services: 10.10.12.0/24

[bluPhy]

We may be hitting this issue: Error updating secondary IP ranges in Google_compute_subnetwork #2570

[wiktorn]

@yardenas @lcaggio @sruffilli I think that this is a bug in networking config for dataplatform, as it references public T-Mobile address space (100.128.0.0/9):

ip_cidr_range: 10.128.48.0/24
secondary_ip_ranges:
   pods: 100.128.48.0/20
   services: 100.255.48.0/24

Either we should use 10.0.0.0/8 network here or 100.64.0.0/10 if the intention was not to use RFC1918 space.

[yardenas]

Thanks everyone!