Closed SiahGD closed 2 years ago
p.s.: same with built in redis on chart version 15.0.0
Same for me
Looks like pinning redis version to 6.2.4 fixes this issue:
kubectl set image sts/sentry-sentry-redis-master redis=docker.io/bitnami/redis:6.2.4
Looks like pinning redis version to 6.2.4 fixes this issue:
kubectl set image sts/sentry-sentry-redis-master redis=docker.io/bitnami/redis:6.2.4
6.2.4 version works for me, thank you
As for AWS Elasticache - it working with 5.0.6
6.2.4 version works for me in chart v15 as well
@mrsrvman Thanx for tha update! How does this affect the helm chart?
need to upgrade sentry to version 22.7.0.
https://github.com/sentry-kubernetes/charts/blob/develop/sentry/Chart.yaml#L6
appVersion: 22.7.0
appVersion: 22.7.0 helped, or downgrade redis to 5.0.6
@SiahGD This breaks snuba-migrate job for me because some GENERIC_METRICS entry isn't in some clickhouse table definition
Version
Using chart 14.1.0 AWS EKS (1.21)
AWS Elasticache redis (6.2.6), non clustered, 2 replicas (3 nodes). Using main endpoint.
Steps to Reproduce
Deploy sentry with terraform (helm_release) Sentry worker crashing with
values
``` prefix: user: create: true email: ${sentry_email} password: ${sentry_password} nginx: enabled: false rabbitmq: enabled: true redis: enabled: true master: disableCommands: [] sentry: web: service: annotations: alb.ingress.kubernetes.io/healthcheck-path: /_health/ alb.ingress.kubernetes.io/healthcheck-port: traffic-port relay: service: annotations: alb.ingress.kubernetes.io/healthcheck-path: /api/relay/healthcheck/ready/ alb.ingress.kubernetes.io/healthcheck-port: traffic-port postgresql: enabled: false externalPostgresql: host: ${postgres_db_host} password: ${postgres_password} username: ${postgres_username} database: ${postgres_db_name} ingress: enabled: true hostname: ${sentry_dns_name} regexPathStyle: aws-alb annotations: kubernetes.io/ingress.class: alb alb.ingress.kubernetes.io/scheme: internet-facing alb.ingress.kubernetes.io/target-type: ip alb.ingress.kubernetes.io/tags: ${tags} alb.ingress.kubernetes.io/inbound-cidrs: ${allowed_cidr_blocks_str} alb.ingress.kubernetes.io/subnets: ${public_subnet_ids_str} alb.ingress.kubernetes.io/listen-ports: '[{"HTTPS": 443}]' alb.ingress.kubernetes.io/ssl-redirect: "443" alb.ingress.kubernetes.io/certificate-arn: ${subdomain_cert_arn} external-dns.alpha.kubernetes.io/hostname: ${sentry_dns_name} filestore: backend: s3 s3: accessKey: ${s3_access_key} secretKey: ${s3_secret_key} bucketName: ${s3_bucket_name} endpointUrl: ${s3_endpoint_url} region_name: ${region} clickhouse: enabled: true clickhouse: imageVersion: "20.8.19.4" configmap: remote_servers: internal_replication: true replica: backup: enabled: true mail: # For example: smtp useTls: true username: ${ses_user} password: ${ses_password} port: 587 host: "email-smtp.us-east-1.amazonaws.com" from: "${ses_from}" backend: "django.core.mail.backends.smtp.EmailBackend" ```Expected Result
workers should process events
Actual Result
see log above