You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Introduced support for Loki by adding an IRSA role and IAM policy for S3 access in the comet_eks module.
- Added variables for enabling Loki and configuring the S3 bucket for Loki logs.
- Implemented monitoring setup with a dedicated namespace and Grafana credentials management.
- Updated outputs to include ARNs and names for the new Loki resources.
- Enhanced the comet_s3 module to create an S3 bucket for Loki logs based on configuration settings.
Copy file name to clipboardExpand all lines: variables.tf
+18Lines changed: 18 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -42,6 +42,24 @@ variable "enable_mpm_infra" {
42
42
default=false
43
43
}
44
44
45
+
variable"enable_loki_bucket" {
46
+
description="Enable creation of S3 bucket for Loki logs (used by comet_s3 module)"
47
+
type=bool
48
+
default=false
49
+
}
50
+
51
+
variable"enable_monitoring_setup" {
52
+
description="Enable monitoring namespace and Grafana credentials secret in EKS (used by comet_eks module)"
53
+
type=bool
54
+
default=false
55
+
}
56
+
57
+
variable"monitoring_namespace" {
58
+
description="Kubernetes namespace for monitoring resources"
59
+
type=string
60
+
default="monitoring"
61
+
}
62
+
45
63
variable"enable_secretsmanager" {
46
64
description="Toggles the comet_secretsmanager module for provisioning Comet Secrets Manager secrets. Requires enable_rds and enable_elasticache to be true."
0 commit comments