 Okay, here is the scenario I want to show you. So, on the left side we have a Kubernetes cluster provided by Gardner, our Kubernetes as a service solution and on the right side we have an existing Cloud Foundry installation with service fabric deployment which can provide some Postgres instances managed by Bosch. So, in our scenario we are developer on Kubernetes and just want to to use a Postgres instance in this case provided by service fabric but unfortunately there is no public endpoint to a Postgres database so there is no easy way to access it and we don't want to set up a Postgres on Kubernetes like just like Jules showed, the YAML involved can get very soon very ugly so we just want to reuse the existing Postgres we have and for that case we use the service manager and provision an instance on Cloud Foundry site and on the way when we provision it we set up a review configuration on both platforms so on Cloud Foundry site and on Kubernetes site in that way that we later on can access the Postgres directly not using the service manager anymore and that I just want to show you so on the terminal on the top we have Kubernetes and on the bottom we have Cloud Foundry and a short notice this is live I've just scripted the commands because I'm very bad in typing and speaking at the same time so I decided to script it beforehand and then have a look and first thing is we just deploy the pod so like Jules showed earlier I just push the image up front so I can just start the application and then we have a look at the application and it says there's an error so let's have a closer look at the error and it says that secrets Postgres not found that's basically the Kubernetes way of saying there's no binding for it so the credentials to the database to connect to is missing so we just need to create and bind the service but how to do this on Kubernetes so on Cloud Foundry that would be quite straightforward which would just look into we can just look into Cloud Foundry and then ask the marketplace what the service fabric provides us for services and there we see that there is some Postgres so we can just create an instance and then bind the service for it but here comes the service manager in place where the service manager connects several service broker and several platforms to each other and then we now we have just a look which platforms are registered in our service manager and we see there are several platforms so most of them Kubernetes but also some Cloud Foundry platforms and the one of interest is this one so this is the demo cluster and we are connected in the other terminal and then we have a look which service brokers are connected to our service manager and there we see that there is a broker, Istio broker which is basically the service fabric plus the Istio configuration so we can provide it, we consume the services from Kubernetes side so with that we can just ask the service catalog which services we can use on Kubernetes side and then we see the same list so we can just create service or how it's called on Kubernetes provisional service and one thing to note here is that we use a dev plan so it's basically just a container and no posh manage instance which would take one or two minutes so this instance should already be there hopefully and then we see the instance is ready and we can just bind it and then the binding have a look at the binding and the binding is there as well so we can have a look at the credentials that were created to access the database and here we see that there is some private IP because like I mentioned there is no public endpoint for the Postgres database but there's no way that this private IP points to the Postgres instance in totally different platform so let's have a look where this IP is actually belonging to and then we just look for the services in our name space and we see one minute ago we have created a service with this specific IP and we set up the Istio configuration in a way that every traffic that is targeting towards this IP is routed to the Cloud Foundry platform and there to the Postgres instances we just created so with that we can have a look at our app and now the secrets are there it should start and it's running in the meantime so we can even access the database and for this demo application it just checks which version of Postgres is used and we see that Postgres is actually accessed and with that I would just already finish the demo and if you are interested in more details or have any questions just join me tomorrow in the demo theater at 12.40 or have a look at GitHub everything I showed you is open source so you can just have a look yourself or get in contact with the corresponding team so thank you and have a nice day