Terraform templates to create F5XC GCP cloud CE (manual mode deployment).
| Name | Version |
|---|---|
| terraform | >= 1.7.0 |
| gcloud | latest |
| curl | >= 1.7 |
| git | >= 8.0 |
| jq | latest |
| Name | Status |
|---|---|
| Linux | supported |
| Mac OS (Sonoma) | supported |
| Windows | unsupported |
- Git (https://git-scm.com/book/en/v2/Getting-Started-Installing-Git)
- Terraform (https://developer.hashicorp.com/terraform/install?product_intent=terraform)
- Google gcloud CLI (https://cloud.google.com/sdk/docs/install)
- F5 XC Credentials (https://docs.cloud.f5.com/docs/how-to/user-mgmt/credentials)
- API Certificate
- SSH public key
- ssh-keygen -t rsa -b 4096 -C "[email protected]"
- F5 XC full tenant name
- Obtain full tenant name in XC web console by navigating to administration page --> tenant settings
- Clone this repo with:
git clone --recurse-submodules https://github.com/f5devcentral/terraform-xc-gcp-ce - Enter repository directory with:
cd terraform-xc-gcp-ce - Follow usage description in topologies section
- Multiple examples in example directory are available. Change to example directory that is to be deployed
with
cd examples/<example_dir_name>
Description of available input variables. Used input variables will change per topology example:
| Name | Description |
|---|---|
| SLO | Site local outside interface (external interface / egress interface) |
| SLI | Site local inside interface (internal interface ( ingress interface) |
| owner | Tag gcp objects with creator / owner email address |
| project_prefix | String added at the beginning of various GCP / F5 XC object identifier. <project_prefix>_<object> |
| project_suffix | String added at the end of various GCP / F5 XC object identifier. <project_prefix>_<object>_<project_suffix> |
Example prefix + suffix for F5XC site name project_prefix_cluster_name_project_suffix |
|
| f5xc_tenant | Full f5 xc tenant name e.g. playground-abcdefg |
| f5xc_api_url | F5 XC API URL e.g. https://https://playground.console.ves.volterra.io/api |
| f5xc_cluster_name | F5 XC cluster name e.g. "gcp-ce-test" |
| f5xc_api_p12_file | Path to F5 XC exported API cert file |
| f5xc_ce_slo_subnet | SLO subnet CIDR e.g. "192.168.0.0/24" |
| f5xc_ce_sli_subnet | SLI subnet CIDR e.g. "192.168.100.0/26" |
| gcp_region | GCP region to deploy site at |
| gcp_zone_node0 | GCP zone for cluster node0 |
| gcp_zone_node1 | GCP zone for cluster node1 |
| gcp_zone_node2 | GCP zone for cluster node2 |
| gcp_instance_image | GCP instance image to use e.g. rhel9-20240216075746-voltstack-combo-us |
| gcp_zone_master_node0 | GCP zone for AppStack master node0 |
| gcp_zone_master_node1 | GCP zone for AppStack master node1 |
| gcp_zone_master_node2 | GCP zone for AppStack master node2 |
| gcp_zone_worker_node0 | GCP zone for AppStack master node0 |
| gcp_zone_worker_node1 | GCP zone for AppStack master node1 |
| gcp_zone_worker_node2 | GCP zone for AppStack master node2 |
| gcp_existing_network_slo | GCP existing network name for SLO |
| gcp_existing_network_sli | GCP existing network name for SLI |
| gcp_existing_subnet_network_slo | GCP existing subnetwork name for SLO |
| gcp_existing_subnet_network_sli | GCP existing subnetwork name for SLI |
| Name | Description |
|---|---|
| Single Node Single NIC new VPC / subnet | Description |
| Single Node Multi NIC new VPC / subnet | Description |
| Single Node Single NIC Existing VPC / new subnet | Description |
| Single Node Multi NIC Existing VPC / new subnet | Description |
| Single Node Single NIC existing VPC / subnet | Description |
| Single Node Multi NIC existing VPC / subnet | Description |
| Single Node Multi NIC existing VPC / new subnet with SLO no IP / GCP NAT RT | Description |
| Single Node Single NIC existing VPC / subnet and 3rd party NAT GW | Description |
| Single Node Multi NIC existing VPC / subnet and 3rd party NAT GW | Description |
| Single Node AppStack Cluster new VPC / subnet | Description |
| Single Node AppStack Cluster existing VPC / new subnet | Description |
| Three Node Cluster Single NIC new VPC / subnet | Description |
| Three Node Cluster Single NIC existing VPC / new subnet | Description |
| Three Node Cluster Single NIC existing VPC / subnet | Description |
| Three Node Cluster Multi NIC new VPC / subnet | Description |
| Three Node Cluster Multi NIC existing VPC / new subnet | Description |
| Three Node Single NIC existing VPC / subnet and 3rd party NAT GW | Description |
| Three Node Multi NIC existing VPC / subnet and 3rd party NAT GW | Description |
| Three Node AppStack Cluster new VPC / subnet | Description |
| Three Node AppStack Cluster existing VPC / new subnet | Description |
| Name | Description |
|---|---|
| Single Node with offline survivability mode and l3 performance enhancement mode | Description |
Find CE cloud-config example for ClickOps deployment at Cloud-Config
For support, please open a GitHub issue. Note, the code in this repository is community supported and is not supported by F5 Networks. For a complete list of supported projects please reference SUPPORT.md.
Please refer to the F5 DevCentral Community Code of Conduct.
Copyright 2014-2020 F5 Networks Inc.
Before you start contributing to any project sponsored by F5 Networks, Inc. (F5) on GitHub, you will need to sign a Contributor License Agreement (CLA).
If you are signing as an individual, we recommend that you talk to your employer (if applicable) before signing the CLA since some employment agreements may have restrictions on your contributions to other projects. Otherwise, by submitting a CLA you represent that you are legally entitled to grant the licenses recited therein.
If your employer has rights to intellectual property that you create, such as your contributions, you represent that you have received permission to make contributions on behalf of that employer, that your employer has waived such rights for your contributions, or that your employer has executed a separate CLA with F5.
If you are signing on behalf of a company, you represent that you are legally entitled to grant the license recited therein. You represent further that each employee of the entity that submits contributions is authorized to submit such contributions on behalf of the entity pursuant to the CLA.