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

Remove customized .yml config files set by operator

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • None
    • 3scale Operator
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started

      3scale operator rewrites three configuration files for system/porta through injecting them from the system ConfigMap to /opt/system-extra-configs path:

      • zync.yml
      • service_discovery.yml
      • rolling_updates.yml

      This can be avoided, because these files are already included in the productized system image.

      In case of `zync.yml` some changes need to be done first - specifically, the operator needs to update the value of the environment variable ZYNC_ENDPOINT, because this is what the operator actually changes (depending on whether zync is enabled or not in the CR).

      For service_discovery.yml there is no need to include it through the operator, as the baked-in version has the same config for the production enviornment.

      As for rolling_updates.yml, it needs to be verified whether the configuration is actually exactly the same, or to update the config in the porta upstream code to be the same as the one set by operator, so this customization can be removed also.

              Unassigned Unassigned
              rhn-support-dmayorov Daria Mayorova
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: