This message was deleted.

@Prashant Shahi may have more insights on this

@Prashant Shahi do you have any ideas regarding this?

Hey @Benedikt 👋 It is out of scope of SigNoz. However, you should be able to follow the guide below: https://medium.com/flant-com/cert-manager-lets-encrypt-ssl-certs-for-kubernetes-7642e463bbce

I could solve the problem on my own by creating a second Service/NodePort:

---
apiVersion: v1
kind: Service
metadata:
  labels:
    <http://app.kubernetes.io/component|app.kubernetes.io/component>: frontend
    <http://app.kubernetes.io/instance|app.kubernetes.io/instance>: signoz-telemetry
    <http://app.kubernetes.io/name|app.kubernetes.io/name>: signoz
  name: signoz-telemetry-frontend-public
spec:
  type: NodePort
  selector:
    <http://app.kubernetes.io/component|app.kubernetes.io/component>: frontend
    <http://app.kubernetes.io/instance|app.kubernetes.io/instance>: signoz-telemetry
    <http://app.kubernetes.io/name|app.kubernetes.io/name>: signoz
  ports:
    - name: client
      protocol: TCP
      port: 80
      targetPort: 3301

it wouldn't require another service, you can use frontend service and ingress alongside Ingress-Nginx Controller.

I will take a look, but it is already working 😉

yup.. familiar with old wisdom "if it works, do not touch it" 😛

Good point, I will check that. Are there any advantages in that solution?

you wouldn't have another service in between so yeah, one less hop.

As far as I understood, my service is not communicating to the signoz service, rather has its on node selector. So shouldn't it be the same?

you are right.. It is using the selector.

Because I've copied some parts of the original svc

now, only advantage would be single service and ingress for frontend as provided from Helm chart.

Yes, that is true. I've not that much experiance with helm and don't know what happens if I change the original service

no worries.. you can keep using the way you are. Or, you can refer to the following equivalent:

clickhouse:
  cloud: aws
  installCustomStorageClass: true
  persistence:
    storageClass: gp2-resizable

frontend:
  service:
    type: NodePort
  ingress:
    enabled: true
    classname: alb
    hosts:
      - host: dev-monitoring.*******.**
        paths:
          - path: /
            pathType: ImplementationSpecific
    # tls:
    #   - secretName: dev-monitoring.*******.**
    #     hosts:
    #       - dev-monitoring.*******.**
    annotations:
      <http://alb.ingress.kubernetes.io/certificate-arn|alb.ingress.kubernetes.io/certificate-arn>: arn:aws:acm:*****************************
      <http://alb.ingress.kubernetes.io/listen-ports|alb.ingress.kubernetes.io/listen-ports>: '[{"HTTP": 80}, {"HTTPS":443}]'
      <http://alb.ingress.kubernetes.io/ssl-redirect|alb.ingress.kubernetes.io/ssl-redirect>: '443'
      <http://alb.ingress.kubernetes.io/scheme|alb.ingress.kubernetes.io/scheme>: internet-facing
      <http://alb.ingress.kubernetes.io/subnets|alb.ingress.kubernetes.io/subnets>: subnet-***, subnet-***