You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the latest docker image: ghcr.io/getsentry/sentry-kubernetes:ff2386f6b1176a36ebfcdb96222ae5840dac8cf1
AWS EKS, version: 1.24
Steps to Reproduce
Run the sentry-kubernetes image in a Kubernetes cluster with cron job monitoring enabled
The container goes into CrashLoopBackOff state
I am confident the pod is configured correctly. We are running the same helm chart in other clusters, with exactly the same configuration, and k8s events are uploaded to sentry.
If I turn off cron job monitoring, the pod starts working.
Environment
Currently the latest docker image: ghcr.io/getsentry/sentry-kubernetes:ff2386f6b1176a36ebfcdb96222ae5840dac8cf1
AWS EKS, version: 1.24
Steps to Reproduce
I am confident the pod is configured correctly. We are running the same helm chart in other clusters, with exactly the same configuration, and k8s events are uploaded to sentry.
If I turn off cron job monitoring, the pod starts working.
Expected Result
The pod should not crash with segmentation fault under no circumstances, especially when the service account is allowed to list cron jobs and jobs.
Actual Result
The text was updated successfully, but these errors were encountered: