VPCΒΆ

OpeNgine has the following options for VPC:

Please note:

  • It is not possible to mix Kubernetes and VPC implementations from different cloud platforms for the same cluster

  • OpeNgine does not automatically validate existing VPC before an attempt to provision Kubernetes cluster. If VPC does not exists or if provisioning service account does not have enough permissions, Kubernetes cluster provisioning will fail.

  • You can define and use VPCs in multiple cloud platforms at the same time, but OpeNgine does not yet implement any interconnections. You will have to implement VPC to VPC connections manually.

In the OpeNgine configuration file environment/vars.yml all VPCs are defined as single vpc: block containing multiple VPC definitions. The block can have a mix of VPCs to be provisioned and references to existing VPCs. The block can contain mix of VPC configurations for different cloud platforms.

VPC configuration in environment/vars.yml file looks like this:

vpc:
  the-first-vpc:
    type: gcp-provision-vpc
    subnets:
      frontend:
        cidr: 10.21.0.0/16
        flow-logs: false
        private-access: true
        region: us-central1
        secondary-ranges:
          pods:
            cidr: 192.168.0.0/17
          services:
            cidr: 192.168.128.0/18
  the-second-vpc:
    type: gcp-existing-vpc
    subnets:
      frontend2:
        cidr: 10.11.0.0/16
        secondary-ranges:
          pods:
            cidr: 192.168.0.0/17
          services:
            cidr: 192.168.128.0/18

The above example configures GCP networks, please refer to corresponding section in documentation for more information.