This message was deleted.

Hey @Rahul Tiwari! Are you following the documentation steps correctly? You would have to create

override-values.yaml

with the YAML present in the steps. https://signoz.io/docs/install/kubernetes/aws/#chart-configuration

@Prashant Shahi i have created the override-values.yaml file and the issue is resolved. Thank you.

kube config directory permissions seems to be insecure. you can resolve with this:

sudo chmod 600 ~/.kube/config

@Prashant Shahi thank you for that also

you will need to run the following to expose the frontend UI locally:

export SERVICE_NAME=$(kubectl get svc --namespace platform -l "<http://app.kubernetes.io/component=frontend|app.kubernetes.io/component=frontend>" -o jsonpath="{.items[0].metadata.name}")

kubectl --namespace platform port-forward svc/$SERVICE_NAME 3301:3301

@Prashant Shahi i run the above but still unable to access signoz dashboard

when you use

port-forward

, frontend UI will be tunnelled to

localhost

in the machine where you execute that command.

i am using aws eks and i have install signoz in one of the amazon linux jumpbox machine

After executing above commands:

kubectl -n platform get svc  -l "<http://app.kubernetes.io/component=frontend|app.kubernetes.io/component=frontend>"

external IP is showing as empty

can you try this again?

kubectl -n platform get svc  -l "<http://app.kubernetes.io/component=frontend|app.kubernetes.io/component=frontend>"

but still external ip is empty and svc is of type CLUSTERIP

it should be updated to

LoadBalancer

no it is still showing type as CLUSTERIP only

@Rahul Tiwari can you run the updated command?

@Prashant Shahi should i take yaml file of frontend svc and edit it to loadbalancer

My typo.. Turns out it is

frontend.service.type

and not

frontend.serviceType

ok

i tried with externalip:3301

@Prashant Shahi it is not working for me, can you send me the service yaml file for exporting the loadbalancer

can you send me output of the following?

kubectl -n platform get pods,svc

[ec2-user@ip-10-0-4-191 ~]$ kubectl -n platform get pods,svc NAME READY STATUS RESTARTS AGE pod/chi-signoz-cluster-0-0-0 1/1 Running 0 131m pod/clickhouse-operator-766b6b8947-26zlj 2/2 Running 0 156m pod/my-release-signoz-alertmanager-0 1/1 Running 0 156m pod/my-release-signoz-frontend-7f484ffb5-7g4jx 1/1 Running 0 156m pod/my-release-signoz-otel-collector-797fc4cdb6-k8626 1/1 Running 0 156m pod/my-release-signoz-otel-collector-metrics-6f5c849cc9-jsvkt 1/1 Running 0 156m pod/my-release-signoz-query-service-0 1/1 Running 0 156m pod/my-release-zookeeper-0 1/1 Running 0 156m NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/chi-signoz-cluster-0-0 ClusterIP None <none> 8123/TCP,9000/TCP,9009/TCP 155m service/clickhouse-operator-metrics ClusterIP 172.20.132.206 <none> 8888/TCP 156m service/my-release-clickhouse ClusterIP 172.20.83.105 <none> 8123/TCP,9000/TCP 156m service/my-release-signoz-alertmanager ClusterIP 172.20.237.241 <none> 9093/TCP 156m service/my-release-signoz-alertmanager-headless ClusterIP None <none> 9093/TCP 156m service/my-release-signoz-frontend LoadBalancer 172.20.18.56 a38e116d2074a41c9a2233850ce5ed9a-210884774.us-west-2.elb.amazonaws.com 3301:32114/TCP 74m service/my-release-signoz-otel-collector ClusterIP 172.20.157.129 <none> 4317/TCP,4318/TCP,55680/TCP,55681/TCP,14250/TCP,14268/TCP,9411/TCP,8888/TCP,8889/TCP 156m service/my-release-signoz-otel-collector-metrics ClusterIP 172.20.33.70 <none> 4317/TCP,4318/TCP,55680/TCP,55681/TCP,14250/TCP,14268/TCP,9411/TCP,8888/TCP 156m service/my-release-signoz-query-service ClusterIP 172.20.24.176 <none> 8080/TCP,8085/TCP 156m service/my-release-zookeeper ClusterIP 172.20.216.19 <none> 2181/TCP,2888/TCP,3888/TCP 156m service/my-release-zookeeper-headless ClusterIP None <none> 2181/TCP,2888/TCP,3888/TCP 156m service/signoz-service LoadBalancer 172.20.166.140 ae38856dfa8794c63b0de5a85c71c588-1600739069.us-west-2.elb.amazonaws.com 3301:31320/TCP 27m [ec2-user@ip-10-0-4-191 ~]$

cluster looks healthy.. Should have worked.

[ec2-user@ip-10-0-4-191 ~]$ kubectl describe svc my-release-signoz-frontend -n platform Name: my-release-signoz-frontend Namespace: platform Labels: app.kubernetes.io/component=frontend app.kubernetes.io/instance=my-release app.kubernetes.io/managed-by=Helm app.kubernetes.io/name=signoz app.kubernetes.io/version=0.8.1 helm.sh/chart=signoz-0.0.17 release=my-release Annotations: kubectl.kubernetes.io/last-applied-configuration: {"apiVersion":"v1","kind":"Service","metadata":{"annotations":{"meta.helm.sh/release-name":"my-release","meta.helm.sh/release-namespace":"... meta.helm.sh/release-name: my-release meta.helm.sh/release-namespace: platform Selector: app.kubernetes.io/component=frontend,app.kubernetes.io/instance=my-release,app.kubernetes.io/name=signoz Type: LoadBalancer IP: 172.20.18.56 LoadBalancer Ingress: a38e116d2074a41c9a2233850ce5ed9a-210884774.us-west-2.elb.amazonaws.com Port: http 3301/TCP TargetPort: 3301/TCP NodePort: http 32114/TCP Endpoints: 10.0.1.17:3301 Session Affinity: None External Traffic Policy: Cluster Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal EnsuringLoadBalancer 29m (x3 over 85m) service-controller Ensuring load balancer Normal EnsuredLoadBalancer 29m (x3 over 85m) service-controller Ensured load balancer [ec2-user@ip-10-0-4-191 ~]$

output for this one?

kubectl -n platform get pods -o wide

[ec2-user@ip-10-0-4-191 ~]$ kubectl -n platform get pods -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES chi-signoz-cluster-0-0-0 1/1 Running 0 162m 10.0.2.241 ip-10-0-2-165.us-west-2.compute.internal <none> <none> clickhouse-operator-766b6b8947-26zlj 2/2 Running 0 3h7m 10.0.2.33 ip-10-0-2-165.us-west-2.compute.internal <none> <none> my-release-signoz-alertmanager-0 1/1 Running 0 3h7m 10.0.1.91 ip-10-0-1-48.us-west-2.compute.internal <none> <none> my-release-signoz-frontend-7f484ffb5-7g4jx 1/1 Running 0 3h7m 10.0.1.17 ip-10-0-1-153.us-west-2.compute.internal <none> <none> my-release-signoz-otel-collector-797fc4cdb6-k8626 1/1 Running 0 3h7m 10.0.3.86 ip-10-0-3-245.us-west-2.compute.internal <none> <none> my-release-signoz-otel-collector-metrics-6f5c849cc9-jsvkt 1/1 Running 0 3h7m 10.0.3.138 ip-10-0-3-245.us-west-2.compute.internal <none> <none> my-release-signoz-query-service-0 1/1 Running 0 3h7m 10.0.1.34 ip-10-0-1-234.us-west-2.compute.internal <none> <none> my-release-zookeeper-0 1/1 Running 0 3h7m 10.0.1.33 ip-10-0-1-48.us-west-2.compute.internal <none> <none> [ec2-user@ip-10-0-4-191 ~]$

So, the

IP

of frontend pod should be part of frontend svc

Endpoints

yes

debugging is not gonna be easy.. as the issue seems to be from your eks cluster.. as it works fine on a fresh eks cluster. it could be version mismatch issue, EKS nodes issue, AWS LoadBalancer side issue, or something entirely different.

For doing this I need to delete that SVC naa

service/signoz-service? why do you even have that 🤔

No i edited only that frontend svc

you can delete, if you had modified it directly before

ok

can you sent it over DM?

ok