Closed lluczaj closed 10 months ago
Assigning to @getsentry/support for routing ⏲️
Hmmm, you're heading into uncharted territory here. The Sentry CLI does not expect the rediss backend, so that's something you'd have to try yourself.
This issue has gone three weeks without activity. In another week, I will close it.
But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community
, I will leave it alone ... forever!
"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀
Since TLS in Redis is officially supported in Sentry don't you have any plans to fix the CLI ? I must say I tried to workaround it but apparently I am missing knowledge about Sentry/Celery and struggle with it a lot 🤔
We don't support kubernetes-based setups - this repository is built around docker-compose only, and tooling (to some degree) works on that assumption. While there are other unaffiliated open-source projects floating around which provide some sample k8s setups, these are not officially supported by this project. Good luck!
@azaslavsky I may not know other Sentry setups good enough but to me this problem is not related to Kubernetes itself. 2 questions to you:
Environment
self-hosted (https://develop.sentry.dev/self-hosted/)
Steps to Reproduce
Expected Result
Get queues list
Actual Result
Error: unknown broker type
Does Sentry CLI expect to get
rediss
backend ? It seems that queues code hasn't been updated for a long time even though Redis TLS is now officially supported.https://github.com/getsentry/sentry/blame/master/src/sentry/monitoring/queues.py#L91
Product Area
Issues
Link
No response
DSN
No response
Version
23.6.2