-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[IBCDPE-938] Deploy Signoz (OTEL Visualization) to kubernetes cluster #35
Changes from all commits
0f93061
73bb182
4e3c472
6b457dd
5b694bb
2f0636a
a002873
b3768c5
d525af3
81a3adc
8c89bc6
23ef64e
ef8bd3f
502276b
7a864e7
c0e2a4c
6bf8506
8b8be2e
4bf72d9
4983fb2
81f24ef
e4f3fbb
75a3063
875010b
41e9147
8814411
0eaafed
6c82806
74c83f3
d4fae1f
1dfa08a
8dfedba
be902b3
ac6a1e3
bf53696
19190c1
fd8fe4f
2f6bae7
5ed270d
a61bdd0
bec8d9d
5b0aa64
aefa2e1
58b2de4
e26e7e4
a501f32
f284709
5aa954b
eebfca1
835de37
e8f989f
5ac8424
5947065
e457ef1
139dd6a
f3f7647
1dab275
63a54ad
d4c79d7
204b2ff
34e27cb
373b800
1b6170e
3482837
5c5654f
f314bde
d4bf895
ae8eacb
fc53860
a295e48
1db7b42
7f652ec
24bc617
b8509df
fe1e37b
4a4da49
5774102
77f2c22
767ac82
908201b
afb6f6e
2cfcaee
436908f
501b1d3
74f33bf
dbe7f70
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,5 @@ | ||
*.tfstate* | ||
.terraform | ||
terraform.tfvars | ||
settings.json | ||
settings.json | ||
temporary_files* |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -31,24 +31,55 @@ module "dpe-sandbox-spacelift-development" { | |
k8s_stack_deployments_name = "DPE DEV Kubernetes Deployments" | ||
k8s_stack_deployments_project_root = "deployments/stacks/dpe-k8s-deployments" | ||
|
||
auth0_stack_name = "DPE DEV Auth0" | ||
auth0_stack_project_root = "deployments/stacks/dpe-auth0" | ||
auth0_domain = "dev-sage-dpe.us.auth0.com" | ||
auth0_clients = [ | ||
{ | ||
name = "bfauble - automation" | ||
description = "App for testing signoz" | ||
app_type = "non_interactive" | ||
scopes = ["write:telemetry"] | ||
}, | ||
{ | ||
name = "schematic - Github Actions" | ||
description = "Client for Github Actions to export telemetry data" | ||
app_type = "non_interactive" | ||
scopes = ["write:telemetry"] | ||
}, | ||
{ | ||
name = "schematic - Dev" | ||
description = "Client for schematic deployed to AWS DEV to export telemetry data" | ||
app_type = "non_interactive" | ||
scopes = ["write:telemetry"] | ||
}, | ||
] | ||
auth0_identifier = "https://dev.sagedpe.org" | ||
|
||
aws_account_id = "631692904429" | ||
region = "us-east-1" | ||
|
||
cluster_name = "dpe-k8-sandbox" | ||
vpc_name = "dpe-sandbox" | ||
|
||
vpc_cidr_block = "10.51.0.0/16" | ||
# public_subnet_cidrs = ["10.51.1.0/24", "10.51.2.0/24", "10.51.3.0/24"] | ||
# private_subnet_cidrs = ["10.51.4.0/24", "10.51.5.0/24", "10.51.6.0/24"] | ||
# azs = ["us-east-1a", "us-east-1b", "us-east-1c"] | ||
# For now, we are only using one public and one private subnet. This is due to how | ||
# EBS can only be mounted to a single AZ. We will need to revisit this if we want to | ||
# allow usage of EFS ($$$$), or add some kind of EBS volume replication. | ||
# Note: EKS requires at least two subnets in different AZs. However, we are only using | ||
# a single subnet for node deployment. | ||
public_subnet_cidrs = ["10.51.1.0/24", "10.51.2.0/24"] | ||
private_subnet_cidrs = ["10.51.4.0/24", "10.51.5.0/24"] | ||
azs = ["us-east-1a", "us-east-1b"] | ||
vpc_cidr_block = "10.52.16.0/20" | ||
# A public subnet is required for each AZ in which the worker nodes are deployed | ||
public_subnet_cidrs = ["10.52.16.0/24", "10.52.17.0/24", "10.52.19.0/24"] | ||
private_subnet_cidrs_eks_control_plane = ["10.52.18.0/28", "10.52.18.16/28"] | ||
azs_eks_control_plane = ["us-east-1a", "us-east-1b"] | ||
|
||
private_subnet_cidrs_eks_worker_nodes = ["10.52.28.0/22", "10.52.24.0/22", "10.52.20.0/22"] | ||
azs_eks_worker_nodes = ["us-east-1c", "us-east-1b", "us-east-1a"] | ||
Comment on lines
+65
to
+72
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This shrinks the VPC size. The order of the AZs also means:
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is fine as-is, but there are 6 availability zones in us-east-1 if you wanted to spread them out more. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That is something I saw mentioned online when starting to tune available spot instances, since each AZ gets their own pool. I hadn't seen any issues with our current setup, but will keep it in mind that we are able to expand out to 6 AZs if we ever need to. |
||
|
||
enable_cluster_ingress = true | ||
enable_otel_ingress = true | ||
Comment on lines
+74
to
+75
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
|
||
ssl_hostname = "dev.sagedpe.org" | ||
auth0_jwks_uri = "https://dev-sage-dpe.us.auth0.com/.well-known/jwks.json" | ||
Comment on lines
+76
to
+77
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Used for SSL termination at the gateway and to validate incoming requests on routes that require a JWT auth header be provided. |
||
deploy_auth0 = true | ||
|
||
ses_email_identities = ["aws-dpe-dev@sagebase.org"] | ||
# Defines the email address that will be used as the sender of the email alerts | ||
smtp_from = "aws-dpe-dev@sagebase.org" | ||
} | ||
|
||
module "dpe-sandbox-spacelift-production" { | ||
|
@@ -69,22 +100,32 @@ module "dpe-sandbox-spacelift-production" { | |
k8s_stack_deployments_name = "DPE Kubernetes Deployments" | ||
k8s_stack_deployments_project_root = "deployments/stacks/dpe-k8s-deployments" | ||
|
||
auth0_stack_name = "DPE Auth0" | ||
auth0_stack_project_root = "deployments/stacks/dpe-auth0" | ||
auth0_domain = "" | ||
auth0_clients = [] | ||
auth0_identifier = "" | ||
|
||
aws_account_id = "766808016710" | ||
region = "us-east-1" | ||
|
||
cluster_name = "dpe-k8" | ||
vpc_name = "dpe-k8" | ||
|
||
vpc_cidr_block = "10.52.0.0/16" | ||
# public_subnet_cidrs = ["10.52.1.0/24", "10.52.2.0/24", "10.52.3.0/24"] | ||
# private_subnet_cidrs = ["10.52.4.0/24", "10.52.5.0/24", "10.52.6.0/24"] | ||
# azs = ["us-east-1a", "us-east-1b", "us-east-1c"] | ||
# For now, we are only using one public and one private subnet. This is due to how | ||
# EBS can only be mounted to a single AZ. We will need to revisit this if we want to | ||
# allow usage of EFS ($$$$), or add some kind of EBS volume replication. | ||
# Note: EKS requires at least two subnets in different AZs. However, we are only using | ||
# a single subnet for node deployment. | ||
public_subnet_cidrs = ["10.52.1.0/24", "10.52.2.0/24"] | ||
private_subnet_cidrs = ["10.52.4.0/24", "10.52.5.0/24"] | ||
azs = ["us-east-1a", "us-east-1b"] | ||
vpc_cidr_block = "10.52.0.0/20" | ||
# A public subnet is required for each AZ in which the worker nodes are deployed | ||
public_subnet_cidrs = ["10.52.0.0/24", "10.52.1.0/24", "10.52.3.0/24"] | ||
private_subnet_cidrs_eks_control_plane = ["10.52.2.0/28", "10.52.2.16/28"] | ||
azs_eks_control_plane = ["us-east-1a", "us-east-1b"] | ||
|
||
private_subnet_cidrs_eks_worker_nodes = ["10.52.12.0/22", "10.52.8.0/22", "10.52.4.0/22"] | ||
azs_eks_worker_nodes = ["us-east-1c", "us-east-1b", "us-east-1a"] | ||
|
||
enable_cluster_ingress = false | ||
enable_otel_ingress = false | ||
ssl_hostname = "" | ||
auth0_jwks_uri = "" | ||
deploy_auth0 = false | ||
|
||
ses_email_identities = [] | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Required for the IaC to set up the SMTP user. Is this acceptable, or should this user be created manually?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My two cents: this is acceptable since it's scoped to a single user resource.