Terraform ICP IBM Cloud

This repository contains a collection of Terraform templates. The Terraform example configurations uses the IBM Cloud provider to provision virtual machines on IBM Cloud Infrastructure (SoftLayer) and Terraform Module ICP Deploy to prepare VSIs and deploy IBM Cloud Private on them. These Terraform templates automate best practices learned from installing ICP on IBM Cloud Infrastructure.

Pre-requisites

• Working copy of Terraform
  • As of this writing, IBM Cloud Terraform provider is not in the main Terraform repository and must be installed manually. See these steps. We tested this automation script against v0.9.1 of the Terraform provider.
• Select a template that most closely matches your desired target environment from the available templates

Using the Terraform templates

1. git clone the repository

2. Navigate to the desired template directory

3. Create a terraform.tfvars file to reflect your environment. Please see specific for the template you select.

4. Run terraform init to download depenencies (modules and plugins)

5. Run terraform plan to investigate deployment plan

6. Run terraform apply to start deployment.

Selecting the right template

We currently have three templates available

• icp-ce-minimal

  • This template will deploy ICP Community Edition with a minimal amount of Virtual Machines and a minimal amount of services enabled
  • Additional ICP services such as logging, monitoring and istio can be enabled as well as dedicated management nodes can be added with minor configuration changes
  • This template is suitable for a quick view of basic ICP and Kubernetes functionality, and simple PoCs and verifications

• icp-ce-with-loadbalancers

  • Like the icp-ce-minimal template, this will deploy a minimal environment, but in this template Loadbalancers will also be created. This creates a topology more similar to the icp-ee environment, where external loadbalancers are a central part of the network design, but with less services and resources active
  • This template is suitable for validation tests and PoCs where external loadbalancer functionality is required

• icp-ee

  • This template deploys a more robust environment, with control plane in a high availabilty configuration
  • By default a separate boot node is provisioned and all SSH communication goes through this
  • This configuration requires access to ICP Enterprise Edition, typically supplied as a tarball

Follow the link to these templates for more detailed information about them.