Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-11573

[operator] external database connection string option in syndesis custom resource

    XMLWordPrintable

Details

    • +
    • Automated

    Description

      (Migrated from https://github.com/syndesisio/syndesis/issues/6477)

      Author: Aiden Keating
      Assignees: unassigned

      This is a...

      [pre][code]
      [x] Feature request
      [ ] Regression (a behavior that used to work and stopped working in a new release)
      [ ] Bug report [!-- Please search GitHub for a similar issue or PR before submitting --]
      [ ] Documentation issue or request
      [/code][/pre]

      Description

      Currently, the Syndesis operator will provision a Postgres database as part of it's setup.

      There is not a way in the Syndesis custom resource to specify that you'd like the operator to not provision this in-cluster Postgres and instead use an external Postgres instance, for example one hosted on AWS, by providing connection string info in the Syndesis CR.

      The feature request would be to add an a boolean option to the [

      db

      object|https://github.com/syndesisio/syndesis/blob/master/install/operator/deploy/crds/syndesis_v1alpha1_syndesis_crd.yaml#L42] in the Syndesis CR, for example

      externalDb

      .

      When set to

      true

      the operator would skip provisioning the in-cluster Postgres and attempt to look for a

      Secret

      in the Namespace with an expected name, for example

      syndesis-database

      . This Secret should contain connection details for an external Postgres instance (username, password, database, host and port)

      The name of the Secret could then be overridden if needed with an optional

      externalDbSecret

      attribute in the

      db

      object.

      For example:

      ``

      db:
          externalDb: true # the operator won't provision a Postgres instance
          externalDbSecret: my-secret-name # the operator will look for a Secret named my-secret-name instead of syndesis-database
      

      `

      This would still be backwards compatible as 

      externalDb

       can be treated as 

      false` when it is not specified in the custom resource.

      Any suggestions about this would be appreciated. I'd be happy to put together a PR around this.

      Attachments

        Issue Links

          Activity

            People

              parichar@redhat.com Paul Richardson
              rhn-support-hbraun Heiko Braun
              Andrej Vano Andrej Vano
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: