bedrock/cluster
amit1411 803102982b
flux still polls from master branch, changed the default branch from master to main (#1453)
2021-06-15 01:07:20 -07:00
..
azure Remove dashboard component from AKS cluster. Not required any longer and breaks deployments with 1.19+ clusters 2021-01-13 11:00:19 -08:00
common flux still polls from master branch, changed the default branch from master to main (#1453) 2021-06-15 01:07:20 -07:00
environments Update aks module to output identities (#1442) 2020-09-22 11:07:24 -07:00
minikube rename `gitops_ssh_key` to `gitops_ssh_key_path` (#1392) 2020-04-28 09:36:31 -07:00
.gitignore
README.md [DOC] Fix typo, state helm version and sample git repo name (#879) 2020-01-13 16:31:55 -08:00

README.md

Getting Started

Bedrock automates Kubernetes cluster deployments with Terraform to provide full reproducibility of cluster operations.

Required Tools

Bedrock uses three tools to automate cluster deployments that you'll need to install if you don't already have them:

Verify that these tools are added to your system's PATH in order to avoid errors during cluster deployment. (Note to WSL users: You will need to either move the executables to /usr/local/bin, or modify ~/.bashrc to add them to PATH and persist the new additions across restarts.)

Releases

To support consistency in the deployment of Terraform based infrastructure. Bedrock has started implementing releases for Terraform scripts. The release process and tools for generating a release are found here.

The first release(s) is 0.11.0 which will be the basic end of life for Terraform 0.11.x support and 0.12.0 which will be the first release supporting Terraform 0.12.x.

Follow Cloud Provider Guide

Bedrock provides templates for creating Kubernetes clusters for each supported cloud provider (currently only Azure -- but we would gratefully accept pull requests for other cloud providers). Follow the instructions for the cloud provider you'd like to create a cluster environment for to get started:

Incorporating Existing Resources

IMPORTANT It is important to note that any resources referenced as a resource in Terraform will assume to be managed by Terraform. So, if one uses an existing cloud resource (resource group, vm, etc) be aware that any updates, changes, or deletions triggered by an operation in Terraform will impact that resource. For instance, if one were to reference an existing Azure Resource Group and perform terraform destroy, the resource group and any resources (even those not managed by Terraform) in that resource group will be deleted.

If you are evaluating Bedrock, it is recommended that you do so in a clean environment. If you want to use existing resources, please read terraform import.