Today, all applications deployed as ClowdApps end up running as Kubernetes Deployments. The application teams lack the option for their ClowdApps to run as StatefulSets

From the docs:

StatefulSets are valuable for applications that require one or more of the following.

• Stable, unique network identifiers.
• Stable, persistent storage.
• Ordered, graceful deployment and scaling.
• Ordered, automated rolling updates.

We've seen demand for StatefulSet support before (https://redhat-internal.slack.com/archives/C022YV4E0NA/p1690200139881719). It has also gained importance recently after the investigation of efficient Kafka consumer group rebalances as part of ADR-026 (StatefulSet benefits summarized in https://docs.google.com/spreadsheets/d/1zP58Qi1yWPH_G7vuVZCVUpaDAzw4aEXyuN1rTUq2w8c/edit#gid=0)