This folder contains the variant to use when deploying in AWS using an EKS cluster.
This module can be declared by adding the following block on your Terraform configuration:
module "thanos" {
source = "git::https://github.com/camptocamp/devops-stack-module-thanos.git//eks?ref=<RELEASE>"
cluster_name = module.eks.cluster_name
base_domain = module.eks.base_domain
cluster_issuer = local.cluster_issuer
argocd_namespace = module.argocd_bootstrap.argocd_namespace
metrics_storage = {
bucket_id = aws_s3_bucket.thanos_metrics_storage.id
region = aws_s3_bucket.thanos_metrics_storage.region
iam_role_arn = module.iam_assumable_role_thanos.iam_role_arn
}
thanos = {
oidc = module.oidc.oidc
}
dependency_ids = {
argocd = module.argocd_bootstrap.id
traefik = module.traefik.id
cert-manager = module.cert-manager.id
oidc = module.oidc.id
}
}
As you can see, a minimum requirement for this module is an S3 bucket with an IAM policy attached and an OIDC provider (more information below).
Important
|
You are in charge of creating a S3 bucket for Thanos to store the archived metrics. We’ve decided to keep the creation of this bucket outside of this module, mainly because the persistence of the data should not be related to the instantiation of the module itself. |
Tip
|
Check the EKS deployment example to see how to create the S3 bucket and to better understand the values passed on the example above. |
Note
|
Do not forget that the bucket configuration also needs to be passed to the module kube-prometheus-stack .
|
Although the declaration above allows you to have a barebones Thanos deployed, it is highly recommended that you customize a few settings for a production-ready deployment. You need to at least configure the resource requirements for a few of the Thanos' components and the size of the persistent volume used by the compactor. You can also configure the compactor retention times, as in the example below.
module "thanos" {
source = "git::https://github.com/camptocamp/devops-stack-module-thanos.git//eks?ref=<RELEASE>"
cluster_name = module.eks.cluster_name
base_domain = module.eks.base_domain
cluster_issuer = local.cluster_issuer
argocd_namespace = module.argocd_bootstrap.argocd_namespace
metrics_storage = {
bucket_id = aws_s3_bucket.thanos_metrics_storage.id
region = aws_s3_bucket.thanos_metrics_storage.region
iam_role_arn = module.iam_assumable_role_thanos.iam_role_arn
}
thanos = {
# OIDC configuration
oidc = module.oidc.oidc
# Configuration of the persistent volume for the compactor
compactor_persistent_size = "100Gi"
# Resources configuration for the pods
compactor_resources = {
limits = {
memory = "1Gi"
}
requests = {
cpu = "0.5"
memory = "512Mi"
}
}
storegateway_resources = {
limits = {
memory = "1Gi"
}
requests = {
cpu = "0.5"
memory = "1Gi"
}
}
query_resources = {
limits = {
memory = "1Gi"
}
requests = {
cpu = "0.5"
memory = "512Mi"
}
}
# Retention settings for the compactor
compactor_retention = {
raw = "60d"
five_min = "120d"
one_hour = "240d"
}
}
dependency_ids = {
argocd = module.argocd_bootstrap.id
traefik = module.traefik.id
cert-manager = module.cert-manager.id
oidc = module.oidc.id
}
}
As you can see on the examples above, the variable thanos
provides an interface to customize the most frequently used settings. This variable is merged with the local value thanos_defaults
, which contains some sensible defaults to have a barebones working deployment. You can check the default values on the local.tf
file.
If there is a need to configure something besides the common settings that we have provided above, you can customize the chart’s values.yaml
by adding an Helm configuration as an HCL structure:
module "thanos" {
source = "git::https://github.com/camptocamp/devops-stack-module-thanos.git//eks?ref=<RELEASE>"
cluster_name = module.eks.cluster_name
base_domain = module.eks.base_domain
cluster_issuer = local.cluster_issuer
argocd_namespace = module.argocd_bootstrap.argocd_namespace
metrics_storage = {
bucket_id = aws_s3_bucket.thanos_metrics_storage.id
region = aws_s3_bucket.thanos_metrics_storage.region
iam_role_arn = module.iam_assumable_role_thanos.iam_role_arn
}
thanos = {
oidc = module.oidc.oidc
}
helm_values = [{ # Note the curly brackets here
thanos = {
map = {
string = "string"
bool = true
}
sequence = [
{
key1 = "value1"
key2 = "value2"
},
{
key1 = "value1"
key2 = "value2"
},
]
sequence2 = [
"string1",
"string2"
]
}
}]
dependency_ids = {
argocd = module.argocd_bootstrap.id
traefik = module.traefik.id
cert-manager = module.cert-manager.id
oidc = module.oidc.id
}
}
Note
|
This module was developed with OIDC in mind. |
There is an OIDC proxy container deployed as a sidecar on each pod that has a web interface. Consequently, the thanos
variable is expected to have a map oidc
containing at least the Issuer URL, the Client ID, and the Client Secret.
You can pass these values by pointing an output from another module (as above), or by defining them explicitly:
module "thanos" {
...
thanos = {
oidc = {
issuer_url = "<URL>"
client_id = "<ID>"
client_secret = "<SECRET>"
}
}
...
}
Since the resource requirements are not the same on every deployment and because the consumed resources also influence the cost associated, we refrained from configuring default resource requirements for the components of Thanos. We did, however, set memory limits for some of the pods (query
, storegateway
and compactor
all have a 1 GB memory limit). We recommend that you customize these values as you see fit.
Important
|
At the very least you should configure the size for the Persistent Volume used by the compactor. |
This value MUST be configured otherwise the compactor will NOT work on a production deployment. The Thanos documentation recommends a size of 100-300 GB.
Obviously, the module depends on an already running Argo CD in the cluster in order for the application to be created.
This module has multiple ingresses and consequently it must be deployed after the module traefik
and cert-manager
.
The following requirements are needed by this module:
The following input variables are required:
Description: AWS S3 bucket configuration values for the bucket where the archived metrics will be stored.
Type:
object({
bucket_id = string
region = string
iam_role_arn = string
})
Description: Name given to the cluster. Value used for the ingress' URL of the application.
Type: string
Description: Base domain of the cluster. Value used for the ingress' URL of the application.
Type: string
The following input variables are optional (have default values):
Description: Namespace used by Argo CD where the Application and AppProject resources should be created.
Type: string
Default: "argocd"
Description: Override of target revision of the application chart.
Type: string
Default: "v2.0.0"
Description: SSL certificate issuer to use. Usually you would configure this value as letsencrypt-staging
or letsencrypt-prod
on your root *.tf
files.
Type: string
Default: "ca-issuer"
Description: Namespace where the applications’s Kubernetes resources should be created. Namespace will be created in case it doesn’t exist.
Type: string
Default: "thanos"
Description: Helm chart value overrides. They should be passed as a list of HCL structures.
Type: any
Default: []
Description: Automated sync options for the Argo CD Application resource.
Type:
object({
allow_empty = optional(bool)
prune = optional(bool)
self_heal = optional(bool)
})
Default:
{
"allow_empty": false,
"prune": true,
"self_heal": true
}
Description: IDs of the other modules on which this module depends on.
Type: map(string)
Default: {}
Description: Most frequently used Thanos settings. This variable is merged with the local value thanos_defaults
, which contains some sensible defaults. You can check the default values on the local.tf
file. If there still is anything other that needs to be customized, you can always pass on configuration values using the variable helm_values
.
Type: any
Default: {}
The following outputs are exported:
Description: ID to pass other modules in order to refer to this module as a dependency. It takes the ID that comes from the main module and passes it along to the code that called this variant in the first place.
Show tables
= Requirements
Name | Version |
---|---|
>= 5 |
|
>= 3 |
|
>= 3 |
|
>= 1 |
= Modules
Name | Source | Version |
---|---|---|
= Inputs
Name | Description | Type | Default | Required |
---|---|---|---|---|
AWS S3 bucket configuration values for the bucket where the archived metrics will be stored. |
|
n/a |
yes |
|
Name given to the cluster. Value used for the ingress' URL of the application. |
|
n/a |
yes |
|
Base domain of the cluster. Value used for the ingress' URL of the application. |
|
n/a |
yes |
|
Namespace used by Argo CD where the Application and AppProject resources should be created. |
|
|
no |
|
Override of target revision of the application chart. |
|
|
no |
|
SSL certificate issuer to use. Usually you would configure this value as |
|
|
no |
|
Namespace where the applications’s Kubernetes resources should be created. Namespace will be created in case it doesn’t exist. |
|
|
no |
|
Helm chart value overrides. They should be passed as a list of HCL structures. |
|
|
no |
|
Automated sync options for the Argo CD Application resource. |
|
|
no |
|
IDs of the other modules on which this module depends on. |
|
|
no |
|
Most frequently used Thanos settings. This variable is merged with the local value |
|
|
no |
= Outputs
Name | Description |
---|---|
ID to pass other modules in order to refer to this module as a dependency. It takes the ID that comes from the main module and passes it along to the code that called this variant in the first place. |