Uploaded image for project: 'Red Hat Internal Developer Platform'
  1. Red Hat Internal Developer Platform
  2. RHIDP-10947

[Operator] Option for configuring StatefulSet instead of Deployment

XMLWordPrintable

    • Option for configuring StatefulSet instead of Deployment
    • M
    • False
    • Hide

      None

      Show
      None
    • False
    • RHDHPLAN-615[Operator] Application continuous availability with deployment using cached (PVC) dynamic-plugins
    • Done
    • RHDHPLAN-615 - [Operator] Application continuous availability with deployment using cached (PVC) dynamic-plugins
    • QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
    • 0% To Do, 0% In Progress, 100% Done
    • Hide
      Starting from version 1.9.0, the Backstage Operator supports deploying the Backstage application using a StatefulSet instead of a Deployment. This provides stable network identities and persistent storage guarantees for Backstage pods, which can be beneficial for PVC based plugin cache storage for example.

      The new `spec.deployment.kind` field in the v1alpha5 API allows you to specify the workload type: Deployment (default) or StatefulSet (new).
      Show
      Starting from version 1.9.0, the Backstage Operator supports deploying the Backstage application using a StatefulSet instead of a Deployment. This provides stable network identities and persistent storage guarantees for Backstage pods, which can be beneficial for PVC based plugin cache storage for example. The new `spec.deployment.kind` field in the v1alpha5 API allows you to specify the workload type: Deployment (default) or StatefulSet (new).
    • Feature
    • Proposed

      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

      Dependencies (internal and external)

      n/a

      Acceptance Criteria

      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>

              gazarenk-1 Gennady Azarenkov
              gazarenk-1 Gennady Azarenkov
              RHDH Install
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: