 Applications typically need to connect to a database to be and possess data. Developers have to manage DB credentials, host names, and even server certificates for those secured databases. This becomes even more complex if we need to deploy the application on a Kubernetes environment like OpenShift. But this doesn't have to be a hassle. In this video, I will show you how you can use WebHack OpenShift Database access and service-bounding operator to make this process easier. I have this gold application here. This application uses CorkwichDB as its backend database. But it doesn't store any connection with the information in its code. What it does is use this service-bounding client library to get the connection string from its deported environment. So let's see how it works. I have this OpenShift cluster environment here. And I'm now in this developer view. And I also have this gold web application deployed in this project. And at this point, this web application doesn't know anything about the connection, so it hasn't started already. But now I'm going to make it work. So the first step is I'm going to create a CorkwichDB instance. I'm going to use the Add menu and then click on Connect Database. I'm going to select CorkwichDB Cloud. And then it connects. OK, the product account is already set up. And then what I need to do is create a database instance. I'm going to name this instance as a food service DB and then create. The instance is now ready. And then the next step is to create a connection for this instance. And then hit Connect. All right, DB connection is ready. And then my application is here. What I need to do is use the service-bounding to bind this connection to this application to create. OK, the bounding is done. And then you can see the application part get restarted and so that you can pick up connection properties. Now let's go to take a look at the deployment object of this application in the environment tab. OK, we can see that the service-bounding woods is not created. And then it's pointing to a binding volume. This is where all the properties are started. And then check the lock. OK, this application successfully started. You can see it get the connection URL with all the credentials, host names. Then most importantly, the SSMO is enabled. And then it's also pointing to the woods certificate. And all right, service started successfully. Now I'm going to launch this application. And then click on the rounds. All right, things look good. The application started. And then load up the default data. Now I'm going to add a new foods to the list. Avocado, save. OK, avocado is now on the list. And things look good. In this video, we saw how a developer could check the database instance self-provisioning and then use the service-bounding gold kind library to securely connect to a Core CoachDB instance without knowing the connection URL beforehand. I hope you found this useful. And thank you so much for watching.