Uploaded image for project: 'FlightPath'
  1. FlightPath
  2. FLPATH-2409

Document db key difference between Helm and RH catalog postgres db installs

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False

      Description of the problem:

      The[ 2 methods our documentation suggests to follow to install the workflow postgres db|https://github.com/rhdhorchestrator/orchestrator-go-operator/blob/main/docs/postgresql/README.md] have diverged slightly.

      If the binami helm chart is used, the user can use the orchestrator CR default userkey/passwordkey values for the postgres db, eg

          authSecret:
            name: sonataflow-psql-postgresql
            passwordKey: postgres-password
            userKey: postgres-username 

       

      But if the user follows the RH catalog postgres method, the default Orchestrator CR values will not work, and they must manually change the orchestrator cr to use the following userkey/passwordkey values:

      authSecret:
         name: "sonataflow-psql-postgresql" 
         userKey: database-user 
         passwordKey: database-password 

       

      We actually do have the parameter requirement documented to user the correct keys in the install doc . But I think we should also have a note clearly stating that the Helm method works with the Orchestrator CR defaults out of the box, while the RH catalog operator method requires manually updating the values. Something very obvious at the top of the document would be useful to avoid an issue.

       

       

              jubah@redhat.com Jennifer Ubah
              chadcrum Chad Crum
              Chad Crum Chad Crum
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: