Prerequisite Infrastructure

The following components are required prior to setting up the infrastructure needed by e6data. These are commonly present in most cloud environments, but if any are not present, please follow the linked guides below to create them.

1. Virtual Private Cloud (VPC)

2. Google Kubernetes Engine (GKE) cluster

   1. Create GKE Cluster

Create a VPC, Subnets & other VPC Resources

Optional, only required if a VPC is not already present to create a GKE Cluster or to install e6data in a new VPC.

For custom-mode VPC networks, first create a network and then establish the desired subnets within a region. You are not required to specify subnets for all regions immediately or at all, but you cannot create instances in a region without defined subnets. Lastly, define the firewall rules for your network.

To create a custom-mode VPC network with only IPv4 subnets, follow these steps.

1. In the Google Cloud console, go to the VPC networks page. Go to VPC networks

2. Click Create VPC network.

3. Enter a Name for the network.

4. Choose Custom for the Subnet creation mode.

5. In the New subnet section, specify the following configuration parameters for a subnet:

   1. Provide a Name for the subnet.

   2. Select a Region.

   3. Enter an IP address range. This is the primary IPv4 range for the subnet.

      If you select a range that is not an RFC 1918 address, confirm that the range doesn't conflict with an existing configuration. For more information, see IPv4 subnet ranges.

   4. To define a secondary range for the subnet, click Create secondary IP range.

      If you select a range that is not an RFC 1918 address, confirm that the range doesn't conflict with an existing configuration. For more information, see IPv4 subnet ranges.

   5. Private Google Access: Choose whether to enable Private Google Access for the subnet when you create it or later by editing it.

   6. Flow logs: Choose whether to enable VPC flow logs for the subnet when you create it or later by editing it.

   7. Click Done.

6. To add more subnets, click Add Subnet and repeat the previous steps. You can also add more subnets to the network after you have created the network.

7. In the Firewall rules section, select zero or more predefined firewall rules in the IPv4 firewall rules. The rules address common use cases for connectivity to instances.

   If you don't select any predefined rules, you can create your own firewall rules after you create the network.

   Each predefined rule name starts with the name of the VPC network that you are creating, NETWORK. In the IPv4 firewall rules tab, the predefined ingress firewall rule named NETWORK-allow-custom is editable. On the right side of the row that contains the rule, click Edit to select subnets, add additional IPv4 ranges, and specify protocols and ports.

   The NETWORK-allow-custom firewall rule is not automatically updated if you later add additional subnets. If you need firewall rules for the new subnets, you must update the firewall configuration to add the rules.

8. Choose the Dynamic routing mode for the VPC network.

   For more information, see dynamic routing mode. You can change the dynamic routing mode later.

9. Maximum transmission unit (MTU): Choose whether the network has an MTU of 1460 (default), 1500, or 8896. Before setting the MTU to a value higher than 1460, review Maximum transmission unit.

10. Click Create.

Please make note of the VPC Region, it will be required when creating the Workspace in the e6data Console.

Create GKE Cluster & Default Node Pool

Optional, only required if a GKE Cluster is not present or to install e6data in a new GKE Cluster.

Create GKE Cluster

To get started with setting up a Google Kubernetes Engine (GKE) cluster along with a default node pool, please follow the comprehensive documentation provided by GCP:

Creating a regional cluster | Google Kubernetes Engine (GKE) | Google Cloud

For high availability, it is advisable to utilize a regional cluster.

Please make note of the GKE Cluster Name, it will be required when creating the Workspace in the e6data Console.