Closed matt-genie closed 2 months ago
I'm running into the same issue. Here's a quick and dirty fix: https://github.com/getsentry/sentry-kubernetes/pull/95
ghcr.io/watonomous/sentry-kubernetes@sha256:a9c62340d633b0dd45a4932f8eee6ad17ac892ce7369331278f8ac46872b512a
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