This Evaluation Guide uses the following network structure and instances.
On Google Cloud, these components can be defined as per the diagram below.
In this section we will create these components, with the exception of the Internal Load Balancer. We will create the Internal Load Balancer later.
The components shown in this diagram are described in the following table.
To create this network structure, the following components must be implemented:
VPC network | lk-vpc | Region | us-west1 (*1) |
Subnet (lk-subnet) | 10.20.0.0/22 | ||
Virtual Machine | Common values across VM | VPC network | lk-vpc |
Subnet | lk-subnet | ||
Network Tags | lk-node | ||
External IP | Ephemeral | ||
node-a | Zone | us-west1-a (*1) | |
Hostname | node-a.internal | ||
Internal IP | 10.20.1.10 | ||
node-b | Zone | us-west1-b (*1) | |
Hostname | node-b.internal | ||
Internal IP | 10.20.2.10 | ||
node-c | Zone | us-west1-c (*1) | |
Hostname | node-b.internal | ||
Internal IP | 10.20.3.10 | ||
Firewall Rules | Common values across Rules | Network | lk-vpc |
Type | Ingress | ||
Target | lk-node | ||
Action | Allow | ||
fw-allow-ssh | Source | WAN IP Address of work location | |
Protocols / ports | all | ||
fw-allow-lk-node-connection | Source | Tags: lk-node | |
Protocols / ports | all | ||
fw-allow-health-check (*2) | Source | 130.211.0.0/22, 35.191.0.0/16 | |
Protocols / ports | all |
- (*1) This example uses us-west1 as Region.
- (*2) This is required to allow the Internal Load Balancer to check the status of each nodes.
The following sections step through the processes necessary for creating these network components, beginning with the first instance.
Post your comment on this topic.