Feat: Enable celery workers and beat

[maltesander]

Description

Added two new roles. worker and beat (max 1 replica).

• New integration test works
• Logging configurable (currently hardcoded info for worker & beat)
• Docs missing, examples etc not updated yet.

Currently, RESULTS_BACKEND only supports Redis, no S3 support.

Definition of Done Checklist

• Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
• Please make sure all these things are done and tick the boxes

Author

• Changes are OpenShift compatible
• CRD changes approved
• CRD documentation for all fields, following the style guide.
• Helm chart can be installed and deployed operator works
• Integration tests passed (for non trivial changes)
• Changes need to be "offline" compatible
• Links to generated (nightly) docs added
• Release note snippet added

Reviewer

• Code contains useful comments
• Code contains useful logging statements
• (Integration-)Test cases added
• Documentation added or updated. Follows the style guide.
• Changelog updated
• Cargo.toml only contains references to git tags (not specific commits or branches)

Acceptance

• Feature Tracker has been updated
• Proper release label has been added
• Links to generated (nightly) docs added
• Release note snippet added
• Add type/deprecation label & add to the deprecation schedule
• Add type/experimental label & add to the experimental features tracker

[adwk67]

Looks good - mainly minor things.

[adwk67]

Openshift tests 🟢 https://testing.stackable.tech/view/02%20Operator%20Tests%20(custom)/job/superset-operator-it-custom/45/

We will bring up the CR open question in the planning meeting.

[adwk67]

LGTM

[maltesander]

Release Notes

Superset now supports running async queries via Celery. Two new roles are introduced, the worker and the beat.
Redis is supported as broker queue and results backend.

Docs

https://docs.stackable.tech/home/nightly/superset/usage-guide/database-connections/