Important
|
The example given below is made to work on AWS, other cloud providers such as Azure will come later. |
-
Access to API keys allowing to create required resources in AWS,
-
Meet the requirements for OCP deployment such as SSH public key and PullSecret from Red Hat,
-
The openshift-install binary is in your
$PATH
, -
The AWS cli binary is in your
$PATH
, -
Knowledge of Terraform basics
# terraform/main.tf
locals {
install_config_path = "install-config.yaml"
region = "eu-west-1"
base_domain = "example.com"
cluster_name = "ocp"
}
module "cluster" {
source = "git::https://github.com/camptocamp/devops-stack.git//modules/openshift4/aws?ref=v0.37.1"
install_config_path = local.install_config_path
base_domain = local.base_domain
cluster_name = local.cluster_name
region = local.region
}
OpenShift is deployed using the openshift-install
binary, which embarks a nested Terraform version. When the DevOps Stack Terraform is running, we cannot follow the child process.
Thus, we can track the deployment progress in terraform/<CLUSTER NAME>/.openshift_install.log
$ tail -f terraform/<CLUSTER NAME>/.openshift_install.log
See the AWS OCP reference page.
See the install-config.yaml customization.
See the AWS Configuration for OCP IPI.