Remove mentions of RHEL 7 and update READMEs

Author: pkhartsk

12/root/usr/share/container-scripts/postgresql/README.md

@@ -1,6 +1,9 @@
 # PostgreSQL 12 SQL Database Server Container Image
 
-This container image features the PostgreSQL 12 SQL database server, suitable for OpenShift and general applications. Users have the option to select from RHEL, CentOS Stream, and Fedora-based images. RHEL images can be found in the [Red Hat Container Catalog](https://access.redhat.com/containers/), while CentOS Stream images are available on [Quay.io](https://quay.io/organization/sclorg), and Fedora images can be accessed in [Quay.io](https://quay.io/organization/fedora). The resulting image can be executed using [podman](https://github.com/containers/libpod).
+This container image features the PostgreSQL 12 SQL database server, suitable for OpenShift and general applications.
+Only RHEL based images are available.
+RHEL images can be found in the [Red Hat Container Catalog](https://access.redhat.com/containers/).
+The resulting image can be executed using [podman](https://github.com/containers/libpod).
 
 Please note that while the examples provided in this README utilize `podman`, it is possible to substitute any instance of `podman` with `docker` and the same arguments. `podman` can be installed with on Fedora with command `dnf install podman-docker`.
 
@@ -224,4 +227,4 @@ Subsequently, log output is redirected to the logging collector process and will
 
 ## Additional Resources
 
-The Dockerfile and other sources related to this container image can be found at https://github.com/sclorg/postgresql-container. In this repository, the RHEL8 Dockerfile is named Dockerfile.rhel8, the RHEL9 Dockerfile is named Dockerfile.rhel9, the RHEL10 Dockerfile is named Dockerfile.rhel10, and the Fedora Dockerfile is named Dockerfile.fedora.
+The Dockerfile and other sources related to this container image can be found at https://github.com/sclorg/postgresql-container. In this repository, the RHEL8 Dockerfile is named Dockerfile.rhel8.

13/root/usr/share/container-scripts/postgresql/README.md

@@ -1,6 +1,6 @@
 # PostgreSQL 13 SQL Database Server Container Image
 
-This container image features the PostgreSQL 13 SQL database server, suitable for OpenShift and general applications. Users have the option to select from RHEL, CentOS Stream, and Fedora-based images. RHEL images can be found in the [Red Hat Container Catalog](https://access.redhat.com/containers/), while CentOS Stream images are available on [Quay.io](https://quay.io/organization/sclorg), and Fedora images can be accessed in [Quay.io](https://quay.io/organization/fedora). The resulting image can be executed using [podman](https://github.com/containers/libpod).
+This container image features the PostgreSQL 13 SQL database server, suitable for OpenShift and general applications. Users have the option to select from RHEL, CentOS Stream, and Fedora-based images. RHEL images can be found in the [Red Hat Container Catalog](https://access.redhat.com/containers/), while CentOS Stream images are available on [Quay.io](https://quay.io/organization/sclorg). The resulting image can be executed using [podman](https://github.com/containers/libpod).
 
 Please note that while the examples provided in this README utilize `podman`, it is possible to substitute any instance of `podman` with `docker` and the same arguments. `podman` can be installed with on Fedora with command `dnf install podman-docker`.
 
@@ -10,10 +10,10 @@ This container image offers a containerized version of the PostgreSQL postgres d
 
 ## Usage
 
-Assuming you are utilizing the `rhel8/postgresql-13` image, which is accessible via the `postgresql:13` imagestream tag in Openshift, the following steps outline usage. To set only the mandatory environment variables without storing the database in a host directory, execute this command:
+Assuming you are utilizing the `rhel9/postgresql-13` image, which is accessible via the `postgresql:13` imagestream tag in Openshift, the following steps outline usage. To set only the mandatory environment variables without storing the database in a host directory, execute this command:
 
 ```bash
-$ podman run -d --name postgresql_database -e POSTGRESQL_USER=user -e POSTGRESQL_PASSWORD=pass -e POSTGRESQL_DATABASE=db -p 5432:5432 rhel8/postgresql-13
+$ podman run -d --name postgresql_database -e POSTGRESQL_USER=user -e POSTGRESQL_PASSWORD=pass -e POSTGRESQL_DATABASE=db -p 5432:5432 rhel9/postgresql-13
 ```
 
 This command creates a container named `postgresql_database` running PostgreSQL with the database `db` and a user with the credentials `user:pass`.
@@ -110,7 +110,7 @@ $ podman run -d --name postgresql_database \
     -e POSTGRESQL_MIGRATION_REMOTE_HOST=172.17.0.2 \
     -e POSTGRESQL_MIGRATION_ADMIN_PASSWORD=remoteAdminP@ssword \
     [ OPTIONAL_CONFIGURATION_VARIABLES ]
-    rhel8/postgresql-13
+    rhel9/postgresql-13
 ```
 
 The migration is performed using the **dump and restore** method (running `pg_dumpall` against the remote cluster and importing the dump locally using `psql`). The process is streamed (via a Unix pipeline), eliminating the need for intermediate dump files and conserving storage space.
@@ -170,7 +170,7 @@ Data files are hard-linked from the old to the new data directory, providing per
 
 ## Extending Image
 
-You can extend this image in Openshift using the `Source` build strategy or via the standalone [source-to-image](https://github.com/openshift/source-to-image) application (where available). For this example, assume that you are using the `rhel8/postgresql-13` image, available via `postgresql:13` imagestream tag in Openshift.
+You can extend this image in Openshift using the `Source` build strategy or via the standalone [source-to-image](https://github.com/openshift/source-to-image) application (where available). For this example, assume that you are using the `rhel9/postgresql-13` image, available via `postgresql:13` imagestream tag in Openshift.
 
 To build a customized image `new-postgresql` with configuration from `https://github.com/sclorg/postgresql-container/tree/master/examples/extending-image`, run:
 
@@ -186,7 +186,7 @@ $ oc new-app postgresql:13~https://github.com/sclorg/postgresql-container.git \
 or via `s2i`:
 
 ```
-$ s2i build --context-dir examples/extending-image/ https://github.com/sclorg/postgresql-container.git rhel8/postgresql-13 new-postgresql
+$ s2i build --context-dir examples/extending-image/ https://github.com/sclorg/postgresql-container.git rhel9/postgresql-13 new-postgresql
 ```
 
 The directory passed to Openshift should contain one or more of the following directories:
@@ -224,4 +224,4 @@ Subsequently, log output is redirected to the logging collector process and will
 
 ## Additional Resources
 
-The Dockerfile and other sources related to this container image can be found at https://github.com/sclorg/postgresql-container. In this repository, the RHEL8 Dockerfile is named Dockerfile.rhel8, the RHEL9 Dockerfile is named Dockerfile.rhel9, the RHEL10 Dockerfile is named Dockerfile.rhel10, and the Fedora Dockerfile is named Dockerfile.fedora.
+The Dockerfile and other sources related to this container image can be found at https://github.com/sclorg/postgresql-container. In this repository, the RHEL8 Dockerfile is named Dockerfile.rhel8, the RHEL9 Dockerfile is named Dockerfile.rhel9, and the CentOS Stream 9 Dockerfile is named Dockerfile.c9s.

15/root/usr/share/container-scripts/postgresql/README.md

@@ -10,10 +10,10 @@ This container image offers a containerized version of the PostgreSQL postgres d
 
 ## Usage
 
-Assuming you are utilizing the `rhel8/postgresql-15` image, which is accessible via the `postgresql:15` imagestream tag in Openshift, the following steps outline usage. To set only the mandatory environment variables without storing the database in a host directory, execute this command:
+Assuming you are utilizing the `rhel9/postgresql-15` image, which is accessible via the `postgresql:15` imagestream tag in Openshift, the following steps outline usage. To set only the mandatory environment variables without storing the database in a host directory, execute this command:
 
 ```bash
-$ podman run -d --name postgresql_database -e POSTGRESQL_USER=user -e POSTGRESQL_PASSWORD=pass -e POSTGRESQL_DATABASE=db -p 5432:5432 rhel8/postgresql-15
+$ podman run -d --name postgresql_database -e POSTGRESQL_USER=user -e POSTGRESQL_PASSWORD=pass -e POSTGRESQL_DATABASE=db -p 5432:5432 rhel9/postgresql-15
 ```
 
 This command creates a container named `postgresql_database` running PostgreSQL with the database `db` and a user with the credentials `user:pass`.
@@ -110,7 +110,7 @@ $ podman run -d --name postgresql_database \
     -e POSTGRESQL_MIGRATION_REMOTE_HOST=172.17.0.2 \
     -e POSTGRESQL_MIGRATION_ADMIN_PASSWORD=remoteAdminP@ssword \
     [ OPTIONAL_CONFIGURATION_VARIABLES ]
-    rhel8/postgresql-13
+    rhel9/postgresql-15
 ```
 
 The migration is performed using the **dump and restore** method (running `pg_dumpall` against the remote cluster and importing the dump locally using `psql`). The process is streamed (via a Unix pipeline), eliminating the need for intermediate dump files and conserving storage space.
@@ -170,7 +170,7 @@ Data files are hard-linked from the old to the new data directory, providing per
 
 ## Extending Image
 
-You can extend this image in Openshift using the `Source` build strategy or via the standalone [source-to-image](https://github.com/openshift/source-to-image) application (where available). For this example, assume that you are using the `rhel8/postgresql-15` image, available via `postgresql:15` imagestream tag in Openshift.
+You can extend this image in Openshift using the `Source` build strategy or via the standalone [source-to-image](https://github.com/openshift/source-to-image) application (where available). For this example, assume that you are using the `rhel9/postgresql-15` image, available via `postgresql:15` imagestream tag in Openshift.
 
 To build a customized image `new-postgresql` with configuration from `https://github.com/sclorg/postgresql-container/tree/master/examples/extending-image`, run:
 
@@ -186,7 +186,7 @@ $ oc new-app postgresql:15~https://github.com/sclorg/postgresql-container.git \
 or via `s2i`:
 
 ```
-$ s2i build --context-dir examples/extending-image/ https://github.com/sclorg/postgresql-container.git rhel8/postgresql-15 new-postgresql
+$ s2i build --context-dir examples/extending-image/ https://github.com/sclorg/postgresql-container.git rhel9/postgresql-15 new-postgresql
 ```
 
 The directory passed to Openshift should contain one or more of the following directories:
@@ -224,4 +224,4 @@ Subsequently, log output is redirected to the logging collector process and will
 
 ## Additional Resources
 
-The Dockerfile and other sources related to this container image can be found at https://github.com/sclorg/postgresql-container. In this repository, the RHEL8 Dockerfile is named Dockerfile.rhel8, the RHEL9 Dockerfile is named Dockerfile.rhel9, the RHEL10 Dockerfile is named Dockerfile.rhel10, and the Fedora Dockerfile is named Dockerfile.fedora.
+The Dockerfile and other sources related to this container image can be found at https://github.com/sclorg/postgresql-container. In this repository, the RHEL8 Dockerfile is named Dockerfile.rhel8, the RHEL9 Dockerfile is named Dockerfile.rhel9, and the CentOS Stream 9 Dockerfile is named Dockerfile.c9s.

16/root/usr/share/container-scripts/postgresql/README.md

@@ -10,10 +10,10 @@ This container image offers a containerized version of the PostgreSQL postgres d
 
 ## Usage
 
-Assuming you are utilizing the `` image, which is accessible via the `postgresql:16` imagestream tag in Openshift, the following steps outline usage. To set only the mandatory environment variables without storing the database in a host directory, execute this command:
+Assuming you are utilizing the `rhel10/postgresql-16` image, which is accessible via the `postgresql:16` imagestream tag in Openshift, the following steps outline usage. To set only the mandatory environment variables without storing the database in a host directory, execute this command:
 
 ```bash
-$ podman run -d --name postgresql_database -e POSTGRESQL_USER=user -e POSTGRESQL_PASSWORD=pass -e POSTGRESQL_DATABASE=db -p 5432:5432 
+$ podman run -d --name postgresql_database -e POSTGRESQL_USER=user -e POSTGRESQL_PASSWORD=pass -e POSTGRESQL_DATABASE=db -p 5432:5432 rhel10/postgresql-16
 ```
 
 This command creates a container named `postgresql_database` running PostgreSQL with the database `db` and a user with the credentials `user:pass`.
@@ -110,7 +110,7 @@ $ podman run -d --name postgresql_database \
     -e POSTGRESQL_MIGRATION_REMOTE_HOST=172.17.0.2 \
     -e POSTGRESQL_MIGRATION_ADMIN_PASSWORD=remoteAdminP@ssword \
     [ OPTIONAL_CONFIGURATION_VARIABLES ]
-    rhel8/postgresql-13
+    rhel10/postgresql-16
 ```
 
 The migration is performed using the **dump and restore** method (running `pg_dumpall` against the remote cluster and importing the dump locally using `psql`). The process is streamed (via a Unix pipeline), eliminating the need for intermediate dump files and conserving storage space.
@@ -170,7 +170,7 @@ Data files are hard-linked from the old to the new data directory, providing per
 
 ## Extending Image
 
-You can extend this image in Openshift using the `Source` build strategy or via the standalone [source-to-image](https://github.com/openshift/source-to-image) application (where available). For this example, assume that you are using the `` image, available via `postgresql:16` imagestream tag in Openshift.
+You can extend this image in Openshift using the `Source` build strategy or via the standalone [source-to-image](https://github.com/openshift/source-to-image) application (where available). For this example, assume that you are using the `rhel10-postgresql-16` image, available via `postgresql:16` imagestream tag in Openshift.
 
 To build a customized image `new-postgresql` with configuration from `https://github.com/sclorg/postgresql-container/tree/master/examples/extending-image`, run:
 
@@ -186,7 +186,7 @@ $ oc new-app postgresql:16~https://github.com/sclorg/postgresql-container.git \
 or via `s2i`:
 
 ```
-$ s2i build --context-dir examples/extending-image/ https://github.com/sclorg/postgresql-container.git  new-postgresql
+$ s2i build --context-dir examples/extending-image/ https://github.com/sclorg/postgresql-container.git rhel10/postgresql-16 new-postgresql
 ```
 
 The directory passed to Openshift should contain one or more of the following directories:
@@ -224,4 +224,4 @@ Subsequently, log output is redirected to the logging collector process and will
 
 ## Additional Resources
 
-The Dockerfile and other sources related to this container image can be found at https://github.com/sclorg/postgresql-container. In this repository, the RHEL8 Dockerfile is named Dockerfile.rhel8, the RHEL9 Dockerfile is named Dockerfile.rhel9, the RHEL10 Dockerfile is named Dockerfile.rhel10, and the Fedora Dockerfile is named Dockerfile.fedora.
+The Dockerfile and other sources related to this container image can be found at https://github.com/sclorg/postgresql-container. In this repository, the RHEL8 Dockerfile is named Dockerfile.rhel8, the RHEL9 Dockerfile is named Dockerfile.rhel9, the RHEL10 Dockerfile is named Dockerfile.rhel10, the CentOS Stream 9 Dockerfile is named Dockerfile.c9s, the CentOS Stream 10 Dockerfile is named Dockerfile.c10s, and the Fedora Dockerfile is named Dockerfile.fedora.

README.md

@@ -6,11 +6,10 @@ Images available on Quay.io are:
 
 - CentOS Stream 9 [postgresql-13](https://quay.io/repository/sclorg/postgresql-13-c9s)
 - CentOS Stream 9 [postgresql-15](https://quay.io/repository/sclorg/postgresql-15-c9s)
-- Fedora [postgresql-11](https://quay.io/repository/fedora/postgresql-11)
-- Fedora [postgresql-12](https://quay.io/repository/fedora/postgresql-12)
-- Fedora [postgresql-13](https://quay.io/repository/fedora/postgresql-13)
-- Fedora [postgresql-14](https://quay.io/repository/fedora/postgresql-14)
+- CentOS Stream 9 [postgresql-16](https://quay.io/repository/sclorg/postgresql-16-c9s)
+- CentOS Stream 10 [postgresql-16](https://quay.io/repository/sclorg/postgresql-16-c10s)
 - Fedora [postgresql-15](https://quay.io/repository/fedora/postgresql-15)
+- Fedora [postgresql-16](https://quay.io/repository/fedora/postgresql-16)
 
 This repository provides Dockerfiles for PostgreSQL container images, optimized for use with OpenShift. These images are available in RHEL, Fedora, and CentOS-based variants.
 
@@ -25,52 +24,53 @@ PostgreSQL versions currently supported are:
 
 - [postgresql-12](https://github.com/sclorg/postgresql-container/tree/master/12)
 - [postgresql-13](https://github.com/sclorg/postgresql-container/tree/master/13)
-- [postgresql-14](https://github.com/sclorg/postgresql-container/tree/master/14)
 - [postgresql-15](https://github.com/sclorg/postgresql-container/tree/master/15)
+- [postgresql-16](https://github.com/sclorg/postgresql-container/tree/master/16)
 
 RHEL versions currently supported are:
 - RHEL8
 - RHEL9
 - RHEL10
 
-CentOS versions currently supported are:
+CentOS Stream versions currently supported are:
 - CentOS Stream 9
+- CentOS Stream 10
 
 ## Installation
 
-Choose either the CentOS Stream 9 or RHEL9-based image:
+Choose either the CentOS Stream or RHEL-based image:
 
-- **RHEL9 based image**
+- **RHEL based image**
 
-  These images are available in the [Red Hat Container Catalog](https://access.redhat.com/containers/#/registry.access.redhat.com/rhel9/postgresql-13).
+  These images are available in the [Red Hat Container Catalog](https://catalog.redhat.com/en/search?searchType=containers).
   To download the image, execute the following command:
 
   ```bash
-  podman pull registry.redhat.io/rhel9/postgresql-13
+  podman pull registry.redhat.io/rhel10/postgresql-16
   ```
 
-  To build a RHEL9-based image, ensure you run Docker build on a RHEL machine with a valid subscription.
+  To build a RHEL-based image, ensure you run Docker build on a RHEL machine with a valid subscription.
 
   ```bash
   $ git clone --recursive https://github.com/sclorg/postgresql-container.git
   $ cd postgresql
-  $ make build TARGET=rhel9 VERSIONS=13
+  $ make build TARGET=rhel10 VERSIONS=16
   ```
 
-- **CentOS Stream 9 based image**
+- **CentOS Stream based image**
 
   These images are available on Quay.io. To download the image, execute the following command:
 
   ```bash
-  $ podman pull https://quay.io/repository/sclorg/postgresql-13-c9s
+  $ podman pull https://quay.io/repository/sclorg/postgresql-16-c10s
   ```
 
   To build a PostgreSQL image from scratch, perform the following steps:
 
   ```bash
   $ git clone --recursive https://github.com/sclorg/postgresql-container.git
   $ cd postgresql
-  $ make build TARGET=c9s VERSIONS=13
+  $ make build TARGET=c10s VERSIONS=16
   ```
 
 Note: While the installation steps utilize `podman`, you can substitute these calls with `docker` with the same arguments.
@@ -101,8 +101,8 @@ For detailed information on the usage of specific PostgreSQL Dockerfiles, please
 
 - [PostgreSQL 12 Usage Documentation](https://github.com/sclorg/postgresql-container/tree/master/12)
 - [PostgreSQL 13 Usage Documentation](https://github.com/sclorg/postgresql-container/tree/master/13)
-- [PostgreSQL 14 Usage Documentation](https://github.com/sclorg/postgresql-container/tree/master/14)
 - [PostgreSQL 15 Usage Documentation](https://github.com/sclorg/postgresql-container/tree/master/15)
+- [PostgreSQL 16 Usage Documentation](https://github.com/sclorg/postgresql-container/tree/master/16)
 
 For unsupported versions, you may refer to:
 
@@ -119,21 +119,21 @@ This repository includes a testing framework that verifies the basic functionali
 
   ```bash
   $ cd postgresql
-  $ make test TARGET=rhel9 VERSIONS=13
+  $ make test TARGET=rhel10 VERSIONS=16
   ```
 
 - **CentOS Stream-based image**
 
   ```bash
   $ cd postgresql
-  $ make test TARGET=c9s VERSIONS=13
+  $ make test TARGET=c10s VERSIONS=16
   ```
 
 - To run a specific subset of test cases, use the `TESTS` parameter:
 
   ```bash
   $ cd postgresql
-  $ make test VERSIONS=13 TESTS="run_general_tests run_replication_test"
+  $ make test VERSIONS=16 TESTS="run_general_tests run_replication_test"
   ```
 
 **Note: By omitting the `VERSIONS` parameter, the build/test action will be performed on all provided versions of PostgreSQL.**