Nagarajan
04/23/2025, 9:16 PM0.78.0
, but I'm unable to add or invite my teammates. Is there any known restriction or limitation regarding user invitations in this version?
Thanks in advance for your help!nitya-signoz
04/24/2025, 4:17 AMNagarajan
04/24/2025, 3:50 PMNagarajan
04/24/2025, 3:59 PMnitya-signoz
04/24/2025, 4:06 PMNagarajan
05/03/2025, 6:28 PMkubectl port-forward from signoz service
, login and all functionality work as expected.
However, when accessing it via Ingress using a custom domain, the following issues occur:
• UI loads, but login sometimes fails or behaves inconsistently.
• After login, i can see something wend wrong page and missing the invite-team-members PAGE or tab but i can see it when i port-forward from serviceNagarajan
05/03/2025, 6:29 PMHere's my helm values yaml
Nagarajan
05/03/2025, 6:29 PMglobal:
storageClass: "${storage_class_name}"
clickhouse:
zookeeper:
replicaCount: 2
resources:
requests:
memory: 4Gi
cpu: "2"
layout:
shardsCount: 1
replicasCount: 2
resources:
requests:
cpu: "2"
memory: 6Gi
persistence:
size: ${clickhouse_persistence_volume}
allowedNetworkIps:
- ${allowed_network_ips}
- "172.20.0.0/16"
signoz:
replicaCount: 2
smtpVars:
enabled: true
SMTP_ENABLED: "true"
SMTP_FROM: "signoz-noreply@test.com"
SMTP_HOST: ${smtp_host}
SMTP_PORT: "587"
SMTP_USERNAME: ${smtp_user}
SMTP_PASSWORD: ${smtp_password}
ingress:
enabled: true
className: nginx
annotations:
service.beta.kubernetes.io/aws-load-balancer-type: nlb
service.beta.kubernetes.io/aws-load-balancer-internal: "true"
external-dns.alpha.kubernetes.io/hostname: ${host_name}
cert-manager.io/cluster-issuer: letsencrypt-prod
nginx.ingress.kubernetes.io/rewrite-target: /
hosts:
- host: ${host_name}
paths:
- path: /
pathType: ImplementationSpecific
port: 8080
tls:
- secretName: signoz
hosts:
- ${host_name}
persistence:
size: ${signoz_persistence_volume}
resources:
requests:
cpu: "2"
memory: 4Gi
alertmanager:
enabled: true
replicaCount: 2
resources:
requests:
cpu: "2"
memory: 3Gi
persistence:
size: ${alertmanager_persistence_volume}
additionalEnvs:
ALERTMANAGER_SMTP_FROM: "signoz-noreply@test.com"
ALERTMANAGER_SMTP_HOST: ${smtp_host}
ALERTMANAGER_SMTP_PORT: "587"
ALERTMANAGER_SMTP_AUTH_USERNAME: ${smtp_user}
ALERTMANAGER_SMTP_AUTH_PASSWORD: ${smtp_password}
otelCollector:
replicaCount: 2
ingress:
enabled: true
className: nginx
annotations:
service.beta.kubernetes.io/aws-load-balancer-type: nlb
service.beta.kubernetes.io/aws-load-balancer-internal: "true"
external-dns.alpha.kubernetes.io/hostname: ${cluster_name}-otelcollector.${domain_name}
cert-manager.io/cluster-issuer: letsencrypt-staging
nginx.ingress.kubernetes.io/ssl-redirect: "true"
nginx.ingress.kubernetes.io/backend-protocol: "GRPC"
hosts:
- host: ${cluster_name}-otelcollector.${domain_name}
paths:
- path: /
pathType: ImplementationSpecific
port: 4317
tls:
- secretName: ${cluster_name}-otelcollector
hosts:
- ${cluster_name}-otelcollector.${domain_name}
resources:
requests:
cpu: "4"
memory: 6Gi
autoscaling:
enabled: true
minReplicas: 2
maxReplicas: 11
targetCPUUtilizationPercentage: 50
targetMemoryUtilizationPercentage: 50
behavior:
scaleDown:
stabilizationWindowSeconds: 300
policies:
- type: Pods
value: 1
periodSeconds: 180
scaleUp:
stabilizationWindowSeconds: 300
policies:
- type: Pods
value: 2
periodSeconds: 60
# keda:
# enabled: true
# pollingInterval: "30"
# cooldownPeriod: "300"
# minReplicaCount: "3"
# maxReplicaCount: "11"
# triggers:
# - type: memory
# metadata:
# type: Utilization
# value: "80"
# - type: cpu
# metadata:
# type: Utilization
# value: "80"Nagarajan
05/03/2025, 6:30 PM