crushten/terraform_eks_deploy

Uses Terraform to deploy EKS resources

terraform_eks_deploy's Issues

Cleanup Kubernetes Terraform configuration

I think we can clean this up a bit not sure though,

Remove Docker provider and use ghcr instead to pull application container

Now that the pipelines are setup for the application should be able to just use that container. Wont need to relie on building the Docker container with Terraform. It was rather flaky anyway.

Use probes to determine application end state

If the application exposes a health check of some sort sould be able to use it to verify the application is up and can be connected to.

Also the liviness and readiness probes should be able to be used.

Add logging/metrics etc for Terraform

• Ensure EKS is logging to CloudTrail/CloudWatch
• Ensure K8S is logging to CloudTrail/CloudWatch

Add remote state support to Terraform so the cluster isnt rebuilt

Have the Terraform state stored locally isnt very helpful or useful if the cluster is running in EKS. Will need to added the ability for Terraform to store its state in AWS. Seems like S3 and DynamoDB can help with this.

Add TLS support to load balancer/application

Would be a good idea to add some sort of TLS support to the application or load balancer. Right now the load balancer runs over http. Also would be good to look at the newer load balancer instead of the "classic" one.

Fix deprecated codeql upload errors

Sigh an oversight by not checking for a newer version of the upload action.

Need to update to v2 it seems

Fix code scanning alert - ECR Repository

Tracking issue for:

• https://github.com/crushten/terraform_EKS_deploy/security/code-scanning/6

Create Github Actions to deploy terraform

Not sure what this will look like. But it will need to use the Github Openid thing.

Fix tfsec/code scanning issues

The code scanning is unhappy with a few things so should fix that.

Add environment support to terraform

Terraform has the concept of workspaces can use those to manage dev,test,staging,prod etc. This would be nice to have and would help with improving the local dev workflow.

Probably shoudl stick to separate vars files/directories maybe