v0.6.0

Update to `context.tf`. Correctly pin Terraform providers. Add GitHub Actions @aknysh (#9)

what

• Update to context.tf
• Correctly pin Terraform providers to support TF 0.13
• Add GitHub Actions
• Use unique name for Fargate IAM role per Kubernetes namespace

why

• Keep up to date
• Standardization
• Use unique name for Fargate IAM role per Kubernetes namespace to allow creating as many IAM roles as Fargate profiles

related

• Closes #3

0.5.0: [AUTOMATED] Update Version Pinning for Terraform to support 0.13 (#5)

* [AUTOMATED] Update Version Pinning for Terraform to support 0.13

## What

1. Update Version Pinning for Terraform to support 0.13

## Why

1. This is a relatively minor update that the CloudPosse module already likely supports.
1. This allows module consumers to not individually update our Terraform module to support Terraform 0.13.

* upgrade to go modules

* update

* upgrade

* Updates README

Co-authored-by: Erik Osterman <[email protected]>

0.4.0 Update terraform-null-label versions to support Terraform 0.13

What

1. Updates terraform-null-label versions 0.14.1, 0.15.0, and 0.16.0 to version 0.17.0
2. This is an automated commit and pull request created by Microplane. More information here.

Why

1. This module and the mentioned previous versions are used extensively across the large majority of Cloud Posse's Terraform Modules. They're currently holding back support for Terraform v0.13. Doing this upgrade in mass will alleviate the pain in our efforts to support Terraform v0.13

0.3.0 Adds null-label environment variable input. Add Go modules for Terratest. Fix example and Terratest

what

• Adds null-label environment variable input
• Add Go modules for Terratest
• Fix example and Terratest

why

• Allows full usage of the null-label inputs
• Go modules allow pinning Go releases for stability
• The example and Terratest were using the old versions of the EKS modules

0.2.0: Updates to ChatOps - Automated commit (#4)

## What
* Adds chatops commands
  - '/test all'
  - '/test bats'
  - '/test readme'
  - '/test terratest'
* Drops codefresh
* Drops slash-command-dispatch
* Removes codefresh badge
* Rebuilds README

## Why
* Change over from codefresh to GH Actions
* Facilitate testing of PRs from forks

0.1.0 Initial implementation of `terraform-aws-eks-fargate-profile`

what

• Initial implementation of terraform-aws-eks-fargate-profile
• Add bats and Terratest
• Add Codefresh test pipeline

why

• Provision an EKS Fargate Profile for Elastic Container Service for Kubernetes

test

• Terratest provisions a Node Group with two worker nodes AND a Fargate Profile for k8sdefault namespace. Then it creates a stub k8s deployment (using k8s go-client) in the default namespace in order for Fargate to add a Fargate node to the cluster to provision the deployment. Then it waits for all three nodes to join the cluster, then deletes the k8s deployment, and finally destroys all AWS resources with terraform destroy

Creating Kubernetes deployment 'demo-deployment' in the 'default' namespace...                                                                                                     
Created Kubernetes deployment 'demo-deployment'                                                                                                                  
Waiting for worker nodes to join the EKS cluster...                                                                                                              
Node ip-172-16-97-1.us-east-2.compute.internal has joined the EKS cluster at 2019-12-10 03:49:29 +0000 UTC                                                       
Node ip-172-16-137-51.us-east-2.compute.internal has joined the EKS cluster at 2019-12-10 03:49:37 +0000 UTC                                                     
Node fargate-ip-172-16-53-87.us-east-2.compute.internal has joined the EKS cluster at 2019-12-10 03:51:06 +0000 UTC                                              
All nodes have joined the EKS cluster                                                                                                                            
Listing deployments in namespace 'default':                                                                                                                       
* Deployment 'demo-deployment' has 1 replica(s)                                                                                                                        
Deleting deployment 'demo-deployment' ...                                                                                                                                           
Deleted deployment 'demo-deployment'     

notes

• Currently, EKS Fargate has a lot of limitations
  https://docs.aws.amazon.com/eks/latest/userguide/fargate.html