Standalone NooBaa Multicloud Object Gateway (MCG) Performance Tuning Guide (without StorageCluster CR) - Quay

Solution Verified - Updated -

Issue

NOTE:

This is a legacy deployment that was configured using section 3.2.2.1.1. Create A Standalone Object Gateway of the Quay documentation.

  This configuration is no longer supported, and will fail the ODF v4.19 upgrade (won't transition to High Availability (HA) NooBaa DB). Migrate to a storagecluster managed MCG using the Migrating from a Quay Standalone Multicloud Object Gateway (MCG) to an ODF StorageCluster ODF MCG - NooBaa solution. and follow the Performance tuning guide for Multicloud Object Gateway solution to tune MCG (NooBaa) properly.

Issue:

The Performance tuning guide for Multicloud Object Gateway assists in tuning NooBaa's Multicloud Object Gateway resources specific to users needs.

In the event, there is a standalone MCG deployment using NooBaa deployed IAW with e.g. Quay Product Documentation that may not include the storagecluster resource which is a workflow requirement to increase NooBaa resources IAW Performance tuning guide for Multicloud Object Gateway this solution will assist.

Without the availability of and/or instead of patching/editing the storagecluster resource, the NooBaa CR can be edited/patched and will be outlined in this solution.

Environment

Red Hat Quay (RHQ) v3.x
Red Hat OpenShift Container Platform (RCOCP) v4.x
Red Hat OpenShift Data Foundation (RHODF) v4.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content