Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-10990

Request for Standardized High Availability Configuration for 3scale Redis Components

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • 2.14.0 GA
    • Backend
    • False
    • None
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started

      Red Hat's recommendation for database usage in production environments and for high availability (HA) is to externalize the databases.

      Presently, the sole approach to ensure 3Scale HA is through their external management.

      For essential database components within 3scale, like backend-redis and system-redis, the current release (version 2.13 and 2.14) requires that high availability (HA) can only be achieved by placing these databases outside of the 3scale environment.

      However, there are customers who lack the resources to manage these databases as a managed service. This situation compels them to exert additional effort to establish a robust and dependable HA architecture for production deployment.

      The customer I represent is searching for a Red Hat standard configuration that ensures high availability for Redis deployments. Providing such configurations would greatly benefit those customers who do not have access to a Managed Redis service, preventing the loss of time and resources in setting up comprehensive solutions independently.

      May be even keeping that part non supportable by Red hat, but at least provide some templates so they can have a base to start with.

              Unassigned Unassigned
              rh-ee-dmansour Djamel-Eddine Mansouri
              Votes:
              4 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: