Allow Zync Database to be configured as an external database on the operator #489
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR intends to allow Zync Database to be configured externally.
Currently it does so by adding a field
.spec.highAvailability.externalZyncDatabaseEnabled
, whose value (true
orfalse
) only takes effect whenspec.highAvailability.enabled
is set totrue
. This implies that with this implementation the only way to set an external zync database is by enabling the other ones to be external too. We can discuss whether we want that to happen or be more granular, taking into account the implications.The reason why behavior of the existing
spec.highAvailability.Enabled
has not been changed to include external zync database is because doing that would break current users deployments (thus why another different new optional parameter is needed)When the zync database is configured externally:
zync-database-postgresql
ImageStream is not created anymorezync-database
DeploymentConfig is not created anymorezync-database
Service is not created anymoreThis is an operator-only functionality.
The possibility of splitting the internal zync database specific components into its own component has been evaluated but to simplify the number of changes needed and diminish the impact on templates side that approach has not been followed.
Let's iterate from here.