Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for external PostgreSQL cluster client-side High Availability #1792

Closed
3 tasks done
AymericP35 opened this issue Mar 25, 2024 · 1 comment · Fixed by #1847
Closed
3 tasks done

Support for external PostgreSQL cluster client-side High Availability #1792

AymericP35 opened this issue Mar 25, 2024 · 1 comment · Fixed by #1847

Comments

@AymericP35
Copy link

Please confirm the following

  • I agree to follow this project's code of conduct.
  • I have checked the current issues for duplicates.
  • I understand that AWX Operator is open source software provided for free and that I might not receive a timely response.

Feature Summary

Add ability to deploy an AWX instance with an external PostgreSQL cluster using client-side High Availability mode.

According to the PostgreSQL documentation, when using client-side High Availability, you must change the target_session_attrs default value any to read-write in order to select the primary postgreSQL server.

To allow such behavior, I suggest the following :

@moonrail
Copy link

fyi, a non-configurable default approach was proposed in 2022 and actually approved, but never merged: #928

I've just now retested if AWX 24 can run with readonly PostgreSQL-Instances and the answer is: No, it cannot.
There is no benefit to not setting target_session_attrs to read-write. And there is no harm in doing so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants