This message was deleted.
# supports
Slackbot
02/15/2024, 5:52 AMThis message was deleted.
b
Bala
02/15/2024, 5:56 AMHere is the ingress config in the values file,
Copy code
ingress:
# -- Enable ingress for Frontend
enabled: true
# -- Ingress Class Name to be used to identify ingress controllers
className: alb
# -- Annotations to Frontend Ingress
annotations:
<http://alb.ingress.kubernetes.io/scheme|alb.ingress.kubernetes.io/scheme>: internet-facing
<http://alb.ingress.kubernetes.io/listen-ports|alb.ingress.kubernetes.io/listen-ports>: '[{"HTTP": 80}, {"HTTPS": 443}]'
hosts:
- host: <http://signoz.monitoring-systems.com|signoz.monitoring-systems.com>
paths:
- path: /
pathType: Prefix
port: 3301
tls:
- hosts:
- <http://signoz.monitoring-systems.com|signoz.monitoring-systems.com>
acmCertArn: arn
acm:us-west-abcd:certificate/1234
backend:
serviceName: signoz-frontend
servicePort: 3301 (edited)Bala
02/15/2024, 5:56 AMThe certificate in use is from ACM and it has been validated
Bala
02/15/2024, 5:58 AMHere is the state of the pods and services,
Copy code
10:48
% kubectl get all -n signoz
NAME READY STATUS RESTARTS AGE
pod/chi-signoz-clickhouse-cluster-0-0-0 1/1 Running 0 147m
pod/signoz-alertmanager-0 1/1 Running 0 147m
pod/signoz-clickhouse-operator-78867977c6-tpcc9 2/2 Running 2 (147m ago) 147m
pod/signoz-frontend-58bcf494db-cnhn5 1/1 Running 0 147m
pod/signoz-k8s-infra-otel-agent-7rz9g 1/1 Running 0 147m
pod/signoz-k8s-infra-otel-agent-9hv8m 1/1 Running 0 147m
pod/signoz-k8s-infra-otel-agent-kh69l 1/1 Running 0 147m
pod/signoz-k8s-infra-otel-agent-rqsl2 1/1 Running 0 147m
pod/signoz-k8s-infra-otel-agent-tp57n 1/1 Running 0 147m
pod/signoz-k8s-infra-otel-agent-wfxqj 1/1 Running 0 147m
pod/signoz-k8s-infra-otel-agent-wrkbc 1/1 Running 0 147m
pod/signoz-k8s-infra-otel-deployment-b776bc9fb-mh2nc 1/1 Running 0 147m
pod/signoz-otel-collector-779f75b5bb-k8lv6 1/1 Running 0 147m
pod/signoz-otel-collector-metrics-667f7f4fdc-lkjzr 1/1 Running 0 147m
pod/signoz-query-service-0 1/1 Running 0 147m
pod/signoz-schema-migrator-init-jzk2w 0/1 Completed 0 147m
pod/signoz-zookeeper-0 1/1 Running 0 147m
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/chi-signoz-clickhouse-cluster-0-0 ClusterIP None <none> 9000/TCP,8123/TCP,9009/TCP 146m
service/signoz-alertmanager ClusterIP a.b.c.d <none> 9093/TCP 147m
service/signoz-alertmanager-headless ClusterIP None <none> 9093/TCP 147m
service/signoz-clickhouse ClusterIP a.b.c.d <none> 8123/TCP,9000/TCP 146m
service/signoz-clickhouse-operator-metrics ClusterIP a.b.c.d <none> 8888/TCP 147m
service/signoz-frontend ClusterIP a.b.c.d <none> 3301/TCP 147m
service/signoz-k8s-infra-otel-agent ClusterIP a.b.c.d <none> 13133/TCP,8888/TCP,4317/TCP,4318/TCP 147m
service/signoz-k8s-infra-otel-deployment ClusterIP a.b.c.d <none> 13133/TCP 147m
service/signoz-otel-collector ClusterIP a.b.c.d <none> 14250/TCP,14268/TCP,8081/TCP,8082/TCP,8888/TCP,4317/TCP,4318/TCP 147m
service/signoz-otel-collector-metrics ClusterIP a.b.c.d <none> 13133/TCP 147m
service/signoz-query-service ClusterIP a.b.c.d <none> 8080/TCP,8085/TCP,4320/TCP 147m
service/signoz-zookeeper ClusterIP a.b.c.d <none> 2181/TCP,2888/TCP,3888/TCP 147m
service/signoz-zookeeper-headless ClusterIP None <none> 2181/TCP,2888/TCP,3888/TCP 147mBala
02/15/2024, 5:58 AMI am not sure why the frontend service is deployed as a Cluster IP
28 Views