https://signoz.io logo
Join Slack
Powered by
Hi Team, we are facing a issue regarding ingress-n...
# support
s
Hi Team, we are facing a issue regarding ingress-nginx, it is creating internal load balancer only with private subnets can anyone please help here. followed https://signoz.io/docs/install/kubernetes/aws/ , https://signoz.io/docs/tutorial/setting-up-tls-for-signoz/ below is the override-values.yaml
Copy code
global:
  storageClass: signoz-gp3
  cloud: aws

clickhouse:
  # layout:
  #   shardsCount: 2
  #   replicasCount: 1
  # zookeeper:
  #   replicaCount: 2
  persistence:
    storageClass: signoz-gp3
    size: 300Gi
  cloudStorage:
    enabled: true
    defaultKeepFreeSpaceBytes: "52428800" # 500MB
    type: s3
    endpoint: <https://ss2-tmp-store/logs-cold-storage/>
    accessKey: <accessKey>
    secretAccess: <secretAccess>
  affinity:
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
        - matchExpressions:
          - key: dedicated
            operator: In
            values:
            - signoz-c6a.2xlarge
  tolerations:
    - key: "signoz"
      operator: "Equal"
      value: "true"
      effect: "NoExecute"
  

schemaMigrator:
  enableReplication: true


cert-manager:
  enabled: true
  installCRDs: true

  letsencrypt: true
  ingressClassName: nginx
  email: <mailto:john@sentisum.com|john@sentisum.com>

ingress-nginx:
  enabled: true
  controller:
    name: ingress-nginx-controller
    namespace: platform
    service:
      annotations:
        <http://service.beta.kubernetes.io/aws-load-balancer-internal|service.beta.kubernetes.io/aws-load-balancer-internal>: "false"  # Ensure this is set to "false" for external LoadBalancer
      type: LoadBalancer
    ingressClassResource:
      name: nginx
      enabled: true
      default: true

frontend:
  ingress:
    enabled: true
    className: nginx
    hosts:
      - host: <http://signoz.sentisum.com|signoz.sentisum.com>
        paths:
          - path: /
            pathType: ImplementationSpecific
            port: 3301
    tls:
      - secretName: <http://signoz.sentisum.com|signoz.sentisum.com>
        hosts:
          - <http://signoz.sentisum.com|signoz.sentisum.com>
    annotations:
      <http://cert-manager.io/cluster-issuer|cert-manager.io/cluster-issuer>: letsencrypt-prod
  affinity:
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
        - matchExpressions:
          - key: dedicated
            operator: In
            values:
            - signoz-c6a.2xlarge
  tolerations:
    - key: "signoz"
      operator: "Equal"
      value: "true"
      effect: "NoExecute"


otelCollector:
  replicaCount: 2
  config:
    exporters:
      clickhousetraces:
        timeout: 30s
      clickhouselogsexporter:
        timeout: 30s
    processors:
      batch:
        timeout: 30s
  ingress:
    enabled: true
    className: nginx
    hosts:
      - host: <http://signoz-ingest.sentisum.com|signoz-ingest.sentisum.com>
        paths:
          - path: /
            pathType: ImplementationSpecific
            port: 4317
    tls:
      - secretName: <http://signoz-ingest.sentisum.com|signoz-ingest.sentisum.com>
        hosts:
          - <http://signoz-ingest.sentisum.com|signoz-ingest.sentisum.com>
    annotations:
      <http://cert-manager.io/cluster-issuer|cert-manager.io/cluster-issuer>: letsencrypt-prod
      <http://nginx.ingress.kubernetes.io/ssl-redirect|nginx.ingress.kubernetes.io/ssl-redirect>: "true"
      <http://nginx.ingress.kubernetes.io/backend-protocol|nginx.ingress.kubernetes.io/backend-protocol>: "GRPC"
  affinity:
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
        - matchExpressions:
          - key: dedicated
            operator: In
            values:
            - signoz-c6a.2xlarge
  tolerations:
    - key: "signoz"
      operator: "Equal"
      value: "true"
      effect: "NoExecute"
p
cert-manager
and 
ingress-nginx
are no longer bundled with the SigNoz helm chart. You will need to install them separately and configure it. It looks like we are yet to update our docs. cc @Vibhu Pandey @Chitransh Gupta
s
yeah, I observed that ingress-nginx service was not coming when installing signoz via helm. so used below command to install ingress-nginx
Copy code
helm install ingress-nginx ingress-nginx/ingress-nginx  -f override-values.yaml --namespace platform
now ingress-nginx-controller and ingress-nginx-controller-admin services are coming up in the service list. but the loadbalancer which is stating external ip, is actually a internal ip. so even though creating a record in route53, not able to export logs or access ui
can you please help me here with correct guidence? Actually signoz is the only way we can see our logs, so its little critical here. for the time being, can you please point me the last signoz version where it is still supported and on the background, we can resolve it.
@Srikanth Chekuri @Prashant Shahi can you please help?
p
In the above ingress-nginx, what is inside the 
override-values.yaml
?
43 Views
Open in Slack
PreviousNext
Powered by