Containerization [music] makes applications scalable, reusable and composable. But when combined with the power to make them portable, it unlocks a whole new world of possibilities. Welcome to NetApp Astro Control. NetApp Astro Control helps in protecting your containerized applications running on Kubernetes. And today we will see how it extends these capabilities to a hybrid cloud environment. While Kubernetes brings a whole lot of benefits, there are a few things that we need to take care of. First, the protection of containerized applications can easily become a complicated task, especially when the applications start to scale and grow. This is mainly attributed to the sheer number of logical components that need to come together in Kubernetes to realize an application. Next, if we can't move these logical components, in turn our application to a cloud of our choice or to an on-premises location, it is a huge setback and we can't really call our applications cloudnative. On the flip side, what if you could break these shackles and automate the protection plan for your containerized applications no matter how complex they are and irrespective of where they are running. To add to it, let us also give you the power to take your applications and their data with you to the platform of your choice whenever you wish to do so. All in a few clicks. That is exactly what we're going to do today by simplifying the complex and putting our apps in cruise control with NetApp Astro Control. First, let's build out the solution on paper. We have an on-remises data center and an Amazon web services platform in the cloud where we will be hosting our applications. There's a customary network backbone in our on-remises infra and we have a VPC instance in AWS for delivering network connectivity to the endpoints. A customer gateway is deployed on prem and a transit gateway is implemented in AWS. We use these endpoints to build a siteto-sightVPN and allow the desired networks over it. We have a netapp all flash fast and a Kubernetes cluster in the on-prem environment. The trident CSI is installed on the Kubernetes cluster via which the AFF backend can be used to deliver persistent storage to the containerized apps. In AWS, we have an instance of cloud volumes on running on EC2 and a Kubernetes cluster running on EC2 as well. Trident is installed within this Kubernetes cluster so that the CVO instance can be used to provision persistent storage for the containerized apps. An instance of NetApp Astro control is used to manage both these Kubernetes clusters and in turn the applications running on them. An S3 bucket is also added to Astro control which will be used to store the application backups. Let's spin up a WordPress application in the AWS Kubernetes cluster that is using the persistent storage delivered by CVO. We can now clone this application to the Kubernetes cluster in onromis. The application data is copied over to the S3 bucket and from there it is copied to a volume provisioned by the AFF and a copy of the WordPress application is brought up in the on-premises Kubernetes cluster using the application metadata captured by Astro Control. Enough seen on paper. Let's see this in action. We are now in NetApp astro control center. I've already added an on-premises Kubernetes cluster to Astrocontrol Center. And this is also the Kubernetes cluster on which Astrocontrol Center has been installed. In the backend section, we can also see the ONAP storage that is configured as a backend for this Kubernetes cluster. We shall now add the Kubernetes cluster that is running in AWS using the cube config file. We will select the storage class back app trident. And once the cluster has been added, we head to the backend section which lists the cloud volumes on tap instance under the discovered section. Let's quickly manage this backend by providing the credentials for authentication. Similarly, let's add another Kubernetes cluster running on promises. This will be our destination to clone the WordPress application. We will also manage the storage backend for this cluster. We now have three Kubernetes clusters. The on-remises Kubernetes cluster is running at our Astro control center. The AWS Kubernetes cluster is where we will create an application first and the on-remises destination Kubernetes cluster will be used as the destination to clone our app. Next, we shall add a bucket to facilitate the storage of application backups. While there are multiple supported options, we shall choose to add an AWS S3 bucket for this demo. We are now all set for porting a containerized application from onremises to the cloud or vice versa. We shall now deploy the WordPress application on the AWS Kubernetes cluster within the WordPress namespace using a Helm chart. Back in Astro Control, let's click on the AWS Kubernetes cluster and go to the namespaces section. The WordPress namespace can be seen. We shall define an application out of this nameace and head to the application section. The WordPress application is now managed by Astrocontrol Center. From the Open Shift UI, we will expose the WordPress application by creating a route for it. We can now access the application using this URL. I've created a new blog and also have it published. Now, let's say that I have a need to move this blog site to my on-remises infrastructure. A point to note here is I can also have a need later to move this blog site back to the cloud. At this juncture, we shall clone this application from AWS to my on-premises Kubernetes cluster. Against the application, we should click on the three dots and choose clone. We are led to a form where we shall provide a name for the clone, the name space in the destination cluster and the destination Kubernetes cluster in onremises as our destination. This will be a clone that will not be based on any existing snapshot or backup. We shall now initiate the clone for the WordPress application. Once the clone is completed, the application state changes to healthy. Do not know the Kubernetes cluster on which it is running. By clicking on the application, we can view the resources and the persistent storage consumed by it. Now the moment of truth. Let us go to the Open Shift cluster in onremises in the WordPress onremises namespace that was created during the clone. We can see that a route has been created automatically. We can access the application by clicking on the URL. We can see the block that was created by us when running in AWS. We will now edit this block page by logging in using the same credentials that was configured for the application when it was set up in AWS. Let us make a small edit to the block page. Let's say this page was edited from the on-romises Kubernetes cluster. Next, we will unmanage the WordPress application running on AWS from Astro Control Center and delete the application itself. We will now clone the on-premises version of the WordPress application to the Kubernetes cluster running in AWS. The process is similar to what we had done before. This time, our destination cluster is the one running on AWS. The application state changes to healthy after the clone has completed. Next, we shall now connect to the Open Shift cluster running on AWS and head to the route section. We will change the name space scope to WordPress AWS that was used during the clone. A route is present and the cloned application should be accessible via this URL. The block site is accessible now. We're able to see our blog page and more importantly we are able to see the line that we added. We have now come a full circle and I've had the WordPress application move around the onremises and cloud Kubernetes infrastructure seamlessly. We have achieved application portability on demand while eliminating complexities along the way. To further simplify, a single pane management solution for all our containerized applications, no matter where they are running, on premises or a cloud of your choice. And to sum it up, with these capabilities, we can now say that our applications are truly cloudnative. For more such videos and to unlock the full potential of your containerized apps on Kubernetes, please visit our demo catalog on NetApp TV by scanning the QR code on the top right. We trust that this new capability of Astrocontrol excites you as much as it excites us as we further integrate with the NetApp data fabric and open the door to more possibilities with containerized applications in a hybrid cloud world. Until I see you in the next video, thank you.