feat(deps)!: sentry update to 24.7.1

[TartanLeGrand]

This PR introduces updates to our Sentry Kubernetes configuration to align with the new features in Sentry 24.7.1. The latest version of Sentry autonomously handles Kafka migrations and topic management, prompting some significant changes in our setup.

Changes:

• 🗑 Removed Kafka Topics Provisioning: Since Sentry 24.6.0 manages Kafka topics internally, I have removed the Kafka topics previously defined in the values.yaml.
• 🔄 Moved and Optimized Jobs: Shifted several jobs to new locations and removed some redundant jobs. Considering the potential for further optimization, possibly through the use of init containers in future updates.
• 📂 Reorganized Chart Directory: Moved charts into a dedicated charts folder to streamline chart linting and testing processes.

Issues Addressed:

• This update resolves the following issues:
  • Issue sentry-nginx Readiness probe failed #1315
  • PR fix!: deployment default values #1379
  • Issue Bitnami version mismatch #1333
  • Additionally, I'm think that the Kafka BC will resolve the relay issue we're seeing in Issue Relay issue after some time #1250.

Pending:

• 🐛 There's an outstanding issue with the onboarding page that seems to stem directly from Sentry. I'm in the process of investigating this bug.

Next Steps:

• 🧹 To maintain clarity and ease of review, I plan to split these changes into smaller, focused PRs before finalizing the merge.

Request for Feedback:

• 🔄 I welcome any feedback on the job optimizations and the proposed use of init containers for future improvements.

Looking forward to your thoughts and suggestions!

[TartanLeGrand]

LGTM, but IDK why the test does not work ...

[Mokto]

I personally think it was better before when we could configure the topics.

Right now with the automated we enforce partition count = 1 everywhere?

[TartanLeGrand]

I personally think it was better before when we could configure the topics.

Right now with the automated we enforce partition count = 1 everywhere?

I thinks for the topics we need to make an PR on the official repo 😄

I have revert my perf optimization and I let 3 replicas for the resources 👍

[TartanLeGrand]

Let's make an inherited BC. I go refactor the PR for fix the Nginx before update. 😄

[TartanLeGrand]

@Mokto add this to the same major release.

[Mokto]

I'm still against merging such a PR. We should be able to set the partition counts.

[adonskoy]

I suggest then to update only the version. 24.8.0 has already been released, and the chart still uses the May release..

[Mokto]

yeah that makes sense.

[TartanLeGrand]

24.8.0 doesn't work because we got an error of ClickHouse. But 24.7.1 does, I intend to migrate to 24.7.1 and fix 24.8.0 with the ClickHouse redesign. 🤔

[Mokto]

@TartanLeGrand just so that we're clear, you still intend to remove your changes related to --create-kafka-topics ?

[TartanLeGrand]

Hello @Mokto, yes am sure it's related to getsentry/self-hosted#3121.

Let to sentry the responsibility of that.

[Mokto]

As I said before, I don't want our users to lose the ability to set custom partition counts.

The self-hosted project is different as everything runs on 1 machine.

[Mokto]

Thanks! I think it's ready to be merged?

[fseguin-pass]

FYI there is a security fix in 24.7.1 cf GHSA-fm88-hc3v-3www

[TartanLeGrand]

Thanks! I think it's ready to be merged?

Nop, fail install with this version

[TartanLeGrand]

@Mokto

I understand your concerns about managing Kafka partitions, but I believe we should let Sentry handle the topic creation as outlined in their Kafka schemas repository.

In my opinion, it's the software's responsibility not the infrastructure's to manage kafka topics provisioning. In a modern software approach, the infrastructure should provide the necessary resources for the software to function properly, while the software takes care of provisioning what it needs to operate efficiently.

[Mokto]

Agreed but right now the software doesn't support it.

[Mokto]

It's now using 24.7.1.