 Today, it's the native cloud apps and as far as the Kubernetes and with MySQL out. So today, we are going through how we do this running native cloud apps with MySQL and running with our buddies in the VP cluster and running on the Kubernetes. So the first topics we will try is to explain the cumulative overview. And the second topic that we do is to go over is how we deploy MySQL and different libraries like new VP clusters using MySQL practices that are on Kubernetes. And we will show the demos how we create the new VP cluster, and as well as how to create and deploy, like using Hamptar or a young man advanced with the Gopalmer or PHP MyAndMean, and looking closely how to do like external names with MySQL. So first, cumulative overview. So what's today, people are looking at and it's like breaking down the system into pieces and looking to get it closely. So that's people's card is microservices and small small pieces and looking at our microservices together and then converting wires and so on, the protocol. And that's the way we talk about it. It's like, okay, people do it with the RESTful, right? And the microservices terms, and in the old days, people used to do SLA or some other corporate in the old days, right? But today, people always talk about, okay, managing the system and by pieces and looking closely. And with the microservices, people have the small subsystem and they're actually within the small subsystem. And what lights in the old days, a big database, centralized database, and as things connects to just one single database, as far as today, people starts to have a small footprint of the database and just so my SQL does. So as the characteristics for these applications on cloud, so people relinquish other services on cloud, no matter this is like, okay, some other AI services like machine learnings, and as far as some other intelligence services or evens, okay, these are the couple of integrations, orchestrations, or curing services from the cloud. And as more deployment we need, yeah, easy deployments will likely continue to deploy, many is very favorable approach. And as all these integrators, microservices are lucidly coupled and API-based services are useful. So on the cloud, how many of my SQL we are doing? So Oracle cloud, we call this Oracle cloud infrastructure, OCI. We have the point fixed, okay, my SQL service, we call this my SQL database service MDS. So it is very just easy to use. We can bring this my SQL with different shapes, okay, all depends what you need. Obviously, CPU, memory, and the computer is just handy because all these like, like backup, security, and things. And the most important thing here is the extensions. We have the update AutoML. And because the accelerations, high performance, and big data. So what we can do is, this my SQL database AutoML, it is actually at the back, okay, we provision a set of cluster machines. And normally, as you store the data. So the data is just, it's not just to store in your DB on the frontier, but as well as to push, okay, to the back of the cluster. So that facilitates, facilitates like in memory code. And it is in memory, and it is very, very super fast. And there's one more additional things. And now, let's say I machine run. So the data, when we talk about machine learning, is to train, okay, the train as a model. So where the data is, likely database, right? So it's actually in this ML. So we provide this like capabilities in all in one, a one set of the solutions as like the NDS, we provide OLTP, OLAP, as well as the machine learning capability and create your apps. So for today, we talk more likely the deployments using container, okay, Kubernetes. And there might be possibilities. It's then and on my SQL server using Docker image. It's just simple. And there's also anonymous properties with master MLDP cluster and it can be deployed using master operator, okay, for the Kubernetes. So what we are going to show you. So the operator, how we do this. So first of all, as to basic master MLDP cluster, there is more new things. But what we do here is to deploy this, okay, on this more easy custom container. And it is up to three in the Kubernetes and balance. The three most stable set components, okay, down at the bottom, MySQL 0, MySQL 1, MySQL 2, okay, the three most cluster can be deployed, okay, and the largest can be three, and the fourth, and the two can be one. So all of this, if you do it on your own, you have, we have to manage every components by ourselves. Okay, as well as the, right, how apps to connect to the routers. So with the MySQL operators, all of this just one kind of one single command, okay, we deploy the whole set of the MLDP because there are three nodes, routers, and also the connectivity house to manage the up and down and bring the server down and then switch over to the other, bring the data back, all this automatically. That's the operators. So how do we do this? So basically, we have the documentation and you can do it with the written on the open source register as the operator is, and we apply, yeah, as the manifest installation, we apply the CLD because from the resource definitions that we create the resource or the IC in the DB cluster companies. And when we close, we run the engine as the operators, as some of the apps are just to help you, okay, to facilities, all the operations, like that, those amount of things. And to create the cluster, it is just simple, create a YAML or FGUs and Hentron. So here, as the manifest, we create a YAML file in that, like the YAML, it will create your cluster name. The second things. So people's may also like to use Hentron, but it's also possible with the MySQL operators. So we have the repository and just to use and install the operator as the, somebody engine, okay, to handle the background drops, the integrations, ground donations, and to install the MySQL in the DB cluster for the, yeah, the Hentron. And then the red text in here. So the TRS use self sign equal to true. So this is some additional possibly, yeah, people may be missed, okay. So I just put it down here. When we create, we can actually set this, okay, because we might not want to provide the certificate. Otherwise, we'll have some more steps, okay, to provide the certificate in order to create the cluster. So as simply as in here, just to set this to true. So look at this, okay, to demo. So let me show the demos, how we do this to create the HTTP clusters using MySQL operators. So we're going to deploy this engine models using the latest versions of our 8.032 operators. So once right now, I have already added the repository. And that's why I just to look up the repository and show them as the operators what it has. There are two TRS in there. One is the operator, one is the MVP cluster. So the first, first, first things, we install the operator engines. So we just have to install operators having the namespace, the name MySQL operators and create a name. So just done. We can actually look at what has been deployed. So we just look at the MySQL operators and see if it is already up and running. So it is up and running. And then at the GitHub website, we can actually copy the tags. And here, that's how we do the Hentra installations for the MVP cluster. It is just real simple. And install just a name. And this actually we use the MySQL MVP cluster. And the namespace just for the name, we have the MyIC01 and the user's group and password super secret. And it can actually be locked in through anywhere. So three instances for the server, one route to the instance. And as mentioned earlier, we use self sign. So once we have done this and the server will be created under this name space, MyIC01. So you can see the facilities are locked. We do not need to create a specific server one, server two, server three. So with this one single command, we create all these servers together and as well as the vouchers. And obviously for the servers, like, okay, how we look up the IP address, that's the IP. So how this is all done. So you can see it is still under the stage of provisioning. So it is on the stage of this initialization of the DB. So after that, okay, in around two minutes time, so you can see that 127 later on, we have three servers up and running. Okay, so it is all entirely being created. Yeah, entirely. And as well as you can see the services, okay, which is actually being created. Going out the route to create the finish. So there are four ports up and running. One is the three server and routers. All ports. And what we do here is we have the new name called, yeah, we have deployment. And we have the IC, the NDP cluster, and which it has three on my port running, and also the routers up and running. So one X is it tries to connect to the bring up and now the port running my full shell ends to connect to the server and then look up what is happening. So it should be secret my cluster. And we tries to look at the cluster status. So they are all up and running with the latest versions, 8.0, 32. And the name right in there. So it is my cluster that's low, that's one, that's two. So let's look at the routers, routers, which is what we are talking about. Do you like for example to get routers? How we do this for families deployments? It is also quite a popular dashboard famous. People may like to use Namibas or Hemchart. We will use Namibas this time and how to add the data source. And add the data source, it is my as well. But one thing is important. These grad families or applications run as separate main space. So you may not know the IP address should be just to use IP address or use a more independent names, what we call externally. Now showing top. So here, this is the deployment of the family using the YAML files. And we have to look at the number file, which is the image grad families, and put number on three thousands. And we may configure some sort of the source CPU and memory, as well as to create load balances so that I can actually lock in from external IP address, like through the Internet to access to it. There are load balances. So what we do actually happens, and we can just to create a namespace of the families and apply the YAML file within that namespace. So you can see, I just to apply this YAML file we just create. And as well as you can see the YAML file create the different level of services including the grad families, so as well as the load balances of this. And once we find this to use, and we can look at the grad family, it is up and running. So still provisioning and getting more and more. And we can stretch to see it. And once we get this to it, what we do here is like how we can connect to the server. So we just look at the IP address, you can see the external IP address. And we just log in. And we can see the cluster IP. Okay. But sometimes, once it's like the IP address, yeah, we never know. Okay. Another day when the server time out again, so the IP address will be changed. But anyway, in here, we can just to use the IP address in here. Do you see, yeah, it's still working in here. So the rest of the speakers which we have just created, and then we save the task, the connection source, that's not nice. So what the next is, we do not like to use the IP address we want something as new. So that my cluster as the service to connect to it. But we are actually in two separate namespace. How can we do this? So what people want to do this is to isolate them by means of usually copying and using the service and the type external name and connecting to that name. We have to define this to my IC01. So we apply this specific, okay, my custom YAML file and to define all of this like same space. So if we look at this, we have more names that we can use. So one of which is my cluster. And my cluster is the point routing to the MySQL router's point. Meaning, whenever there is any switching up and down, it will post to the right server and getting that to use. So that works. That should work. And we may get hookups to write specific a scaling, performance scaling, a specific table regarding like memory usage, something like that. So just take an example. So we add PC columns, allocations, how many, how much memory is free out and for specific events as well. So on this, we may actually be able to see that. Okay. We have a report, okay, getting data. So in these tries to create this. So all this, and we may actually create another one, select a version and other panels. So within the dashboard, that's actually about the server name, host name, and as well support and versions. So once we have this, this is going to my cluster as the server name. So what we do here is we may change the primary cluster, okay, to somewhere else. This is nice to show connections to it and connections to it and then switch this primary instance to another server. So once up to this, once we do this, we will have the server and change this to my cluster tool for just an example. So you can actually change it to cluster too. So what we do here, the server just switched. And if we refresh the page and what it does, the server connects to this, yeah, my cluster as the router needed here, it connects to the right servers, okay, which is the primary server. So we can actually change another time. And so from the application point of view, it is similar. It is just this abuse and automatic sending. Okay. The last bit of piece I want to show is the way we are using the PHP. So here's a not quick demo. When we deploy PHP, my admin is to my SQL in the GP cluster. And last time, we have been using YAML and this time, as the services. We may actually do this by hand chart as well. We can put in PHP, my admin, find somewhere else, and we have the BNAMI, hand chart, okay. And we have the hand chart creations where we just reset the DB host equal to my cluster. Again, my cluster is the name. So basically, the provisions using the hand chart values, the values between the original and the added, I just put the added, okay, to the hand chart report values to put in the certificates for the connections. So the PHP, my admin thing connects to the server directly as the SSL connections. So I also put the load balancers to enables the browsers from the internet, my missions can connect to it. So we can see the IP address and finally, we get hookups through these servers. So what we have the service up and running. So here IP address and the load balancers which is one, two, and nine, some other things. And we just copy and paste and put it onto the into the page and we will find we're locked in. But the thing is, we haven't yet to put in the external names. That's why when we connect, it fails. Now we go back in here, we need to put my extra, okay, it's the reference, okay, regardless the mouse, you still want my cluster on my service. So what we have is events in my cluster, we are most, which has all the external names for the servers. So we just register all this to the PHP, my admin home space. And once we have all this done, we can run this PHP again. So it is just easy and handy. So it is all created. So with this, we just be lucky again. And then it is SSL connections. I hope this can go with the questions and see if any of you have any questions for us.