 So MTC is known to migrate application from one OpenShift cluster to another cluster, but in this case now with this new feature I can migrate an application on the same cluster, but changing the underlying storage for one or multiple applications So here's I just went to the operator hub I've already installed the migration toolkit for containers So if I would go to the install operators now, you can see it's already deployed If I click on it all I did after that is to Create the instance of the migration controller So the migration controller by clicking that button will install the controller inside MTC And will deploy the UI for me to and all the other components I need to actually execute this this migration so here I actually just Use the route of this application now of my MTC operator To connect to the UI with the same credit and shoulder that would connect to my cluster And the host where this is installed is already pre-configured for me and as I'm migrating to the same cluster I'm doing in place migration. I don't even have to add additional cluster I'm just gonna migrate from this cluster to this cluster, which is the host I'm on right now Then I'm gonna create a migration plan And I will pick an application and change the underlying storage. So here. Let's do that I'll call this plan demo and And This is the new this is where I will find a new capability, right? So MTC has been known so far for migrating to do full migration including pvs from one cluster to another I can do state migration, which was a feature. We already had in 1.6 Allowing me to migrate the state or just the pvs from one cluster to another But potentially we deploy my application from pipeline on my secondary cluster So sometimes it's only the state that I need to migrate But from but with the storage class conversion feature now, I can stay on the same cluster I don't even have to migrate to another cluster. I can just select that I will select the host I'm on right now, which is the only cluster available. Anyway, I'm gonna click next and Here I only have two simplistic Projects which are websites. I'm gonna click on the first one and this is the one I want to migrate the underlying storage, right? so let's click next again and MTC will look for all the pvs that exist inside that that namespace and will allow me to to pick a new New storage class for those pvs So let's give it a second So here only one pv was found I could potentially have multiple pvs with some other applications but in this case, it's only one pv claimed by a mi SQL at a base and And There's the type of storage class class doesn't really matter Actually, what is used behind the scene is our sync to copy the data at the file system level So this would be working from any storage class to any storage class. So think about changing technology from one type of storage to another one or Changing to another storage class that would have more space into it If I'm running out of space, so there's all kinds of use cases Where this is applicable. So in this case here, I'm just gonna select another storage class, which is Which can be anything that I would have available in my cluster. I'm gonna click next And that's pretty much it now my plan has been created and I will be ready to execute this migration And again in this case, I only selected one namespace But I could also do mass migration of storage class classes So if I would want to migrate a large amount of application from one storage class to another then I could do that as well So now that my plan is ready, I can execute this plan. So I can either Stage so what stage you would do is pre copy the data to my new storage class and We'll reduce the downtime when I do cut over as this is our thing that is actually doing the migration It it depends on the kind of file system I have at the amount of files and so if I have multiple files, it might be better to do stage To reduce the amount of downtime because when I do cut over to do the final copy I will need to shut down the application to finalize that copy before we can relaunch it again This is to make sure that we don't have any data That is still in memory or any log files So there's a little bit of downtime, but that can be reduced by doing the stage process first in this case for demo purposes I'm just gonna click cut over and I'll and I will click the migrate button. So this will take a Little bit of time a few seconds or a few minutes depending on how much data needs to be copied over If I would want to see what's happening during this process, then I can click on the migration button here and I can go down to see in details. What is happening during the migration? So all and if anything goes wrong, you can also look at the migration resources That are behind where I could potentially look at the logs or the describe of the of the CR to understand Exactly what happened behind the scene, but hopefully this will go well here We'll let this run and then we'll come back at the end of the migration. So that's it This is how you can actually do in place storage migration using the new MTC 1.7 race. Thank you