You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wait and check the workload's deployment using these commands:
NS=demo-4
APP=spring-tap-petclinic
tanzu apps -n $NS workload get $APP
## Get the URL of the service and open the URL in your browser
kc get ksvc/$APP -n $NS -o json | jq .status.address.url
Resources checked and their result:
kc get ClusterResource/postgresql: Yes
Remark: The ClusterResource corresponds to what tanzu services types list | grep postgresql command displays
kc get resourceclaim -n demo-4: No
kc get Postgres/postgres-db -n demo-4: YES
Conclusion
The Spring Boot Petclinic Application has been well deployed, the URL of the service is accessible
No resourceclaim has been needed to do the binding using SBO. The PostgresDB resource has been used directly
to bind the DB with the Knative Service.
Scenario
Title: Spring Boot Petclinic application and postgresql running within the same namespace
Reference: TAP documentation to play the different scenario using RabbitMQ - here
Steps:
demo-4
ApiVersion:Kind:NameofTheResource
Expected
Results:
Wait and check the workload's deployment using these commands:
Resources checked and their result:
kc get ClusterResource/postgresql
: YesRemark: The ClusterResource corresponds to what
tanzu services types list | grep postgresql
command displayskc get resourceclaim -n demo-4
: Nokc get Postgres/postgres-db -n demo-4
: YESConclusion
The Spring Boot Petclinic Application has been well deployed, the URL of the service is accessible
No resourceclaim has been needed to do the binding using SBO. The PostgresDB resource has been used directly
to bind the DB with the Knative Service.
See the SBO spec section
To cleanup
The text was updated successfully, but these errors were encountered: