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

Implement reliable container waiting strategy for OpenShift PostgreSQL images from Red Hat registry #1183

Open
michalvavrik opened this issue Jun 27, 2024 · 0 comments
Labels
priority/urgent highest priority

Comments

@michalvavrik
Copy link
Contributor

OpenShift container image of PostgreSQL provided by Red Hat registry like https://catalog.redhat.com/software/containers/rhel9/postgresql-15/63f763f779eb1214c4d6fcf6?architecture=amd64&image=66612c686fe614446062820c&container-tabs=overview and https://catalog.redhat.com/software/containers/rhel9/postgresql-16/657b03866783e1b1fb87e142?architecture=amd64&image=66612ca95ea3c2839df21ce1 redirects database logs into different folder and stops logging into STDOUT. Which means that our log waiting strategy like listening on IPv4 address cannot be executed because that message is in a file. We need to implement reliable way to check that container is ready.

@michalvavrik michalvavrik added the priority/urgent highest priority label Jun 27, 2024
@michalvavrik michalvavrik changed the title Implement reliable container waiting strategy for OpenShift PostgreSQL images from Red Hat Implement reliable container waiting strategy for OpenShift PostgreSQL images from Red Hat registry Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/urgent highest priority
Projects
None yet
Development

No branches or pull requests

1 participant