Celery worker - redis connection isn't being reestablished, celery 5.5 / kombu upgrade

[alextreme]

Product versie / Product version

2.5.0

Omschrijf het probleem / Describe the bug

Taiga Dimpact 227 + 229

Silvia has investigated multiple issues on Dimpact PodiumD in which the Objects API celery worker connection to Redis was broken (by a deployment or a restart of the cluster) after which the connection was not reestablished.

This leads to objects being created but no notifications being sent to Open Notificaties and subscribed applications. The problem is resolved after a restart of the objects api celery worker pod.

Sergei has struggled with this same issue with Open Forms and has attempted to update Open Froms to a rc of Celery 5.5: https://github.com/open-formulieren/open-forms/pull/4937/files

This discussion at celery states the issue and solution:
celery/celery#7276 (comment)

Because of the issues I'd like to (pre)release a objects-api with celery 5.5, at least to verify that this solves the issue or as an alternative until celery 5.5 comes out properly

Stappen om te reproduceren / Steps to reproduce

No response

Verwacht gedrag / Expected behavior

No response

[stevenbal]

I was thinking of making a patch release 3.0.2 for #538 this week anyway, so I could include the kombu upgrade in there as well. I'm not sure though if Dimpact still relies on the v1 endpoints though, so should I make backport the kombu upgrade and make a version 2.5.1 as well?

[alextreme]

Lets leave it at a 3.0.x patch