Fixed exposed host binding item for databases provisioned by Cloud Native Postgres Operator #1081
Conversation
…tive Postgres Operator The appropriate database host name is stored in `.status.writeService` field, and it is NOT equal to `Postgres` resource name. Changes: * servicebinding host annotation got updated * added `provider` binding, the value is set to `enterprisedb` * generic test application is extended with `/postgres-ready` endpoint that returns `OK` if the connection to Postgres database can be established using the provided bindings * New version of the test application got pushed to the registry for all supported arches * Cloud Native Postgres acceptance test got update to assert the database connection Signed-off-by: Predrag Knezevic <[email protected]>
Codecov Report
@@ Coverage Diff @@
## master #1081 +/- ##
=======================================
Coverage 58.92% 58.92%
=======================================
Files 30 30
Lines 1670 1670
=======================================
Hits 984 984
Misses 560 560
Partials 126 126 Continue to review full report at Codecov.
|
|
@pmacik could provsion an ARM based cluster and the generic test application works there as well? |
yes, I'll do that |
|
I can confirm, that new generic test app works on |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pmacik The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The appropriate database host name is stored in
.status.writeServicefield, and it is NOTequal to
Postgresresource name.Changes:
providerbinding, the value is set toenterprisedb/postgres-readyendpoint thatreturns
OKif the connection to Postgres database can be established using the provided bindingsFixes #1077