-
Feature Request
-
Resolution: Unresolved
-
Major
-
None
-
2.12.0 GA
-
5
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Engineering
 Requires coordination between System team and Operator team.
Current behavior
By default 3scale provides the Zync component responsible to sync data from 3scale to other systems. It is also responsible for creating the routes for APIcast managed by 3scale, master, admin & developer portals.
Desired behavior
Add an option to not deploy zync components at all.
As Zync configuration is injected by 3scale-operator, it can be done by operator itself, by removing this line: https://github.com/3scale/3scale-operator/blob/73d07acff4af050affdab5cded0833a1cd1ad5ec/pkg/3scale/amp/component/system.go#L1150
Note that if Zync configuration doesn't have a "endpoint" property, the Zync jobs are skipped with a message WARN: Skipping Zync for event XXX. URL not configured. Obviously, that warning should be ignored if zync is disabled.
- incorporates
-
THREESCALE-9560 Perform PATCH on client update instead of PUT
- Closed
- is related to
-
THREESCALE-8420 Zync-que errors with Endpoint is not a valid URL
- To Develop
- relates to
-
THREESCALE-8717 Provide granular control of PDBs when not using specific pods
- Closed
-
THREESCALE-11398 Add UI feature to enable/disable synchronization per service
- Defined
-
THREESCALE-8102 Make route creation in zync optional.
- To Test (QE)
-
THREESCALE-11502 Add flag to 3scale-operator to disable zync
- New