Open cmoulliard opened 2 years ago
If the app tries to connect to localhost then most likely the secret wasn't mounted. This servicebinding takes place after the first deployment of the knative service, so you might have multiple revisions for the app. See if the most recent revision works. I remember seeing two or three revisions/deployments for the knative service where the last one did get the secret mounted and did connect to the database.
See if the most recent revision works. I remember seeing two or three revisions/deployments for the knative service where the last one did get the secret mounted and did connect to the database.
Will this problem been fixed with TAP v1.0.2 as the error is really annoying ? @trisberg
I agree, this is annoying. The fix won't be in 1.0.2 unfortunately. We are waiting for some changes in carvel-kapp before we can address this. I'm hoping for TAP 1.1 having a better experience.
Issue
The spring-boot-jpa pod cannot access the Posgtresql DB deployed on TAP - v1.0.1 using the ServiceBinding
Log of the pod
Workload file
Secret created by the SBO
Datasource as defined within the
application-postgresql.properties
Deployment and SBO yaml
See this gist containing the YAML content of the deployment and ServiceBinding : https://gist.github.com/cmoulliard/8e1093d6a7a4aaf1909a021ad04a8ea6#file-gistfile0-txt-L303-L305
FYI: The build of the spring boot worked well using pakeeto buildpacks ad the Service Binding layer has been well added: https://gist.github.com/cmoulliard/6dc089a9e81054687decd67e7f049dfc#file-gistfile0-txt-L1525
Questions:
localhost:5432
and notpostgres-db.tap-demo:5432
?