Fix prometheus deployment strategy

Set minimum health percent to 0 for prometheus (#21)

* Set minimum health percent to 0 for prometheus

In the current setup, Prometheus uses a single efs file system, which means that there can only be one Prometheus container running simultaneously in the cluster.

Without this the rolling updates don't work because ECS cannot drain the node where Prometheus is working

* Clarify comment

Update default teleport version to 3.1.8

2.0.3

Update default teleport version and user-data module

2.0.2

Bump teleport_bootstrap_script to v3.3.5 (#18)

2.0.1

Minor Monitoring update:

• Fixes alertmanager slack username

2.0.0 Adding monitoring for ECS

This release adds Monitoring for ECS. More details about this release can be found in the associated PR #16

1.3.0 adding user-data

This release introduces the user-data module that allows to create some basic configurations to connect the ecs node to the cluster, add a security iptable patch and (if available) connect the node directly to teleport for remote accessing.

1.2.2 Introduce a shorter IAM role name

Shorten IAM role name by removing terraform.env var from it

1.2.1

This release just adds the ecs_instance_profile_arn output for the ecs-cluster module

1.2.0: Module to create an ECR repository with attached policies (#11)

* Module to create an ECR repository with attached lifecycle policy and IAM pull & push policies.

* Made variables & outputs names consistent with underscores.

* Using aws_iam_policy_document data source.

* Making the ecr repository lifecycle policy optional.

* Dropped the `repository_description` variable.

1.1.1

use a list for sg