Open michalvavrik opened 1 week ago
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.
listening on IPv4 address
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 addresscannot be executed because that message is in a file. We need to implement reliable way to check that container is ready.