Doddophonique/tah-deploy
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Improved readability
Some checks reported errors
--> Linted: ANSIBLE No errors were found in the linting process
Details
--> Linted: GITLEAKS No errors were found in the linting process
Details
--> Linted: JSCPD No errors were found in the linting process
Details
--> Linted: MARKDOWN Errors were detected, please view logs
Details
--> Linted: NATURAL_LANGUAGE Errors were detected, please view logs
Details
Lint Code Base / run-lint (push) Failing after 32s
Details

Browse Source
This commit is contained in:
Davide Oddone 2024-10-18 16:48:23 +02:00
parent 8de6a0166a
commit 5c69bb29ff
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@ -1,7 +1,7 @@
# Terraform-Ansible-Helm Deployer # Terraform-Ansible-Helm Deployer
[![Super-Linter](https://github.com/doddophonique/tah-deploy/actions/workflows/super-linter.yml/badge.svg)](https://github.com/marketplace/actions/super-linter) [![Super-Linter](https://github.com/doddophonique/tah-deploy/actions/workflows/super-linter.yml/badge.svg)](https://github.com/marketplace/actions/super-linter)
## Usage ## Usage
Everything can be done from the `terraform/` folder: From the `terraform/` folder:
``` ```
$ terraform init $ terraform init
$ terraform plan $ terraform plan
@ -10,7 +10,7 @@ $ terraform apply
## Decisions and goals ## Decisions and goals
The `terraform-provider-libvirt` has been chosen over Vagrant to deploy the VMs as a way to simplify the structure of the project. The choice over a cloud provider such as AWS or GCP has been done to not incur into billing cost during troubleshooting and deployments. The `terraform-provider-libvirt` has been chosen over Vagrant to deploy the VMs as a way to simplify the structure of the project. The choice over a cloud provider such as AWS or GCP has been done to not incur into billing cost during troubleshooting and deployments.
### Terraform script
The Terraform script roughly follows these steps: The Terraform script roughly follows these steps:
1. Deploy 3 VMs (one master and two workers) with: 1. Deploy 3 VMs (one master and two workers) with:
- 2 vCPUs; - 2 vCPUs;
@ -25,10 +25,10 @@ The Terraform script roughly follows these steps:
3. Create the `kiratech-test` namespace; 3. Create the `kiratech-test` namespace;
4. Run the CIS Kubernetes benchmark; 4. Run the CIS Kubernetes benchmark;
5. Copy the helm folder to the master node and install helm. 5. Copy the helm folder to the master node and install helm.
### Next steps
The script currently lacks: The script currently lacks:
1. Capability of deploying an Helm application; - [] Capability of deploying an Helm application;
2. Usage of Terraform outputs to populate Ansible files; - [] Usage of Terraform outputs to populate Ansible files;
### CIS Kubernetes Benchmark ### CIS Kubernetes Benchmark
The CIS Benchamrk is one of (if not the) most popular benchmarks publicly available, and also has a simple way to implement it in a deployment pipeline using the [kube-bench](https://github.com/aquasecurity/kube-bench) implementation. The CIS Benchamrk is one of (if not the) most popular benchmarks publicly available, and also has a simple way to implement it in a deployment pipeline using the [kube-bench](https://github.com/aquasecurity/kube-bench) implementation.