Uploaded image for project: 'Project Quay'
  1. Project Quay
  2. PROJQUAY-8732

Quay Operator Reconciliation Fails When Using Managed Database with Additional Connection Arguments

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • Quay Hosted

      QuayRegistry : -
       

      apiVersion: quay.redhat.com/v1
kind: QuayRegistry
metadata: 
  creationTimestamp: "2025-03-21T14:12:22Z"
  finalizers: 
  - quay-operator/finalizer
  generation: 3
  name: example-registry
  namespace: quay-enterprise
  resourceVersion: "152492"
  uid: 1c0709d8-e4e1-4c0f-aba3-9566141739d7
spec: 
  components: 
  - kind: quay
    managed: true
  - kind: postgres
    managed: true
  - kind: clair
    managed: true
  - kind: redis
    managed: true
  - kind: horizontalpodautoscaler
    managed: true
  - kind: objectstorage
    managed: true
  - kind: route
    managed: true
  - kind: mirror
    managed: true
  - kind: monitoring
    managed: true
  - kind: tls
    managed: true
  - kind: clairpostgres
    managed: true
  configBundleSecret: example-registry-config-bundle-67sps

      Added below parameters to the config bundle
       

      DB_CONNECTION_ARGS: 
    stale_timeout: 60
    max_connections: 5

       
      Triggers the below error in the quayregistry
       

          message: postgres component marked as managed, but `configBundleSecret` contains
      required fields
    reason: ConfigInvalid

       
      Edit (ibazulic): The expectation is that addition of connection args is allowed, even if the db is managed. We need to have a way to limit the stale time and the pool size without resorting to marking the db as unmanaged.

              Unassigned Unassigned
              rhn-support-snangare Sameer Nangare
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: