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

Use code rolling updates instead of templates volume mounts

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • None
    • 2.5 GA
    • OSE Templates
    • None
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started

      Context

      We use rolling updates in porta to enable/disable features for container builds
      But on-premises builds are using volume mounts to set those values. Which sometimes lead in desynchronization and mistakes. See https://github.com/3scale/3scale-operator/pull/117#issuecomment-478922952

      Goal

      • remove the templates volume mounts, having one default from the code. Less maintenance, one source of truth
      • defaults can be merged with existing extras configs.
      • document how to enable/disable certain features on-premises

      Dev notes

      The ideal solution would be:

      • defaults are read from the config/*.yml
      • custom are read from /opt/system/extra-configs/*.yml and merged to the defaults.

              msorianod Miguel Soriano
              hramihaj Hery Ramihajamalala (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: