XML

Word

Printable

Epic Name:
Option for configuring StatefulSet instead of Deployment
Size:
M
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Parent Link:
RHIDP-10934[Operator] Application continuous availability with deployment using cached (PVC) dynamic-plugins
Epic Status:
To Do
Feature Link:
RHIDP-10934 - [Operator] Application continuous availability with deployment using cached (PVC) dynamic-plugins
Planning:

QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
Hierarchy Progress Bar:

25% To Do, 75% In Progress, 0% Done
Intelligence Requested:
Market:

EPIC Goal

To make it possible to optionally configure apps.StatefulSet instead of apps.Deployment K8s as a resource for deployment Backstage (RHDH) instance.

The idea is to make it a part of Backstage CR spec like:

spec:
  deployment:
     kind: StatefulSet

and spec.deplyment.patch field already allows configure it properly for any of them.

In general, StatefulSet "extends" Deployment so it could be done with minimal overhead for user.

Background/Feature Origin

As described in parent feature

n/a

Release Enablement/Demo - Provide necessary release enablement details
and documents

DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue>

DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue>

DEV - Downstream build attached to advisory: <link to errata>

QE - Test plans in Playwright: <link or reference to playwright>

QE - Automated tests merged: <link or reference to automated tests>

DOC - Downstream documentation merged: <link to meaningful PR>

depends on

RHIDP-9950 Introduce Backstage v1alpha5