Skip to content

Conversation

FxKu
Copy link
Member

@FxKu FxKu commented Aug 25, 2021

fix #1060 Trigger running lookup function when new database are specified

fix 2: Try to delete the pooler secret only if master and/or replica pooler have been enabled in oldSpec but are both disabled in new spec.

fix 3: Do not sync the pooler when there's no change. This big condition to check if sync is needed did not work properly because we have initialized the connection pooler in several places to an empty struct (acidv1.ConnectionPooler{}) although being absent in the manifest. On sync it is compared to the newSpec where it's nil. It only worked when there was an update and we got the oldSpec from K8s, where it was also nil.
Solution: If nil create an empty struct to be used with e.g. generating environment variables. Do not set cluster.Spec.ConnectionPooler = &acidv1.ConnectionPooler{}

fix 3b: Do not sync when there's no pooler at all. The condition mentioned above did not check the case when there is no connection pooler running or has been disabled an not needed in newSpec.

@FxKu FxKu added this to the 1.7 milestone Aug 25, 2021
@FxKu FxKu added the zalando label Aug 25, 2021
@RafiaSabih
Copy link
Contributor

👍

1 similar comment
@FxKu
Copy link
Member Author

FxKu commented Aug 27, 2021

👍

@FxKu FxKu merged commit 62ed7e4 into master Aug 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Pooler issue after upgrade to 1.5. With "error: unexpected response from login query".

2 participants