https://signoz.io logo
Join Slack
Powered by
I want to take a moment to thank Signoz's team. I ...
# general
o
I want to take a moment to thank Signoz's team. I am truly amazed by its functionality, ease of use, and the positive impact on our 1. developer's productivity, 2. less time trying to debug issues. 3. optimizing and improving our database and GraphQL queries 4. Cost saving ( stakeholders are happy with the impact). Please know that your efforts are deeply appreciated and highly valued.🙇
In between, I am trying to expose our signoz clickhouse setup via our ingress controller, @Prashant Shahi, I have applied the following ingress yaml file but it seems not to work. Do I need to do any other setup
Copy code
kind: Ingress
metadata:
  name: chi-signoz-clickhouse-cluster
  labels:
    <http://clickhouse.altinity.com/app|clickhouse.altinity.com/app>: chop
    <http://clickhouse.altinity.com/chi|clickhouse.altinity.com/chi>: signoz-clickhouse
    <http://clickhouse.altinity.com/cluster|clickhouse.altinity.com/cluster>: cluster
    <http://clickhouse.altinity.com/namespace|clickhouse.altinity.com/namespace>: infra
    <http://clickhouse.altinity.com/replica|clickhouse.altinity.com/replica>: "0"
    <http://clickhouse.altinity.com/shard|clickhouse.altinity.com/shard>: "0"
  annotations:
    <http://cert-manager.io/cluster-issuer|cert-manager.io/cluster-issuer>: "cert-manager-dns"
    <http://kubernetes.io/tls-acme|kubernetes.io/tls-acme>: "true"
spec:
  ingressClassName: nginx
  tls:
    - hosts:
        - "<http://clickhouse-staging.companydomain.com|clickhouse-staging.companydomain.com>"
      secretName: clickhouse-staging-tls-setup
  rules:
    - host: "<http://clickhouse-staging.companydomain.com|clickhouse-staging.companydomain.com>"
      http:
        paths:
          - path: /
            pathType: ImplementationSpecific
            backend:
              service:
                name: chi-signoz-clickhouse-cluster-0-0
                port:
                  number: 80
p
it could be caused by the followings: • port number 
80
in ingress • not allowing "Your IP" in the 
clickhouse.allowedNetworkIps
helm configuration
@oluchi orji may I know your use case with exposed clickhouse? it is generally recommended not expose it to public internet.
o
Hello @Prashant Shahi, thanks for your response, we are trying to connect to the clickhouse using client libraries written in golang or python,. we no longer want to run the clickhouse query via the pod shell
p
@oluchi orji are you using the same clickhouse server for your application? It is not recommended to use one for production setup, but I don't think it is gonna be an issue in dev environment.
if your application running in K8s as well? If not, you will have to update 
clickhouse.allowedNetworkIps
configuration
also, have you tried updating the port number from the above ingress manifest?
4 Views
Open in Slack
PreviousNext
Powered by