Develop Azure Infrastructure as a Service compute solutions

32. AZ-203 - Lab - Working with the service principal of the Kubernetes cluster

Now here we are again in Azure. Now the first thing we're going to ensure is that the Azure Kubernetes service has the required permissions to pull out the image from the Azure Container history. So first we're going to issue some commands to ensure that the service principle that's assigned to Azure Kubernetes has the required privilege to pull out images from Azure Container History. So first I'm going to go ahead and set some environment variables. So first is the resource group. This is the resource group for our community cluster. Next is the name of our cluster. Next is the resource group of our Azure container tree. And finally, the name of our Azure Container history. Next, I'll make sure that I get the client ID. So that's the client ID of the service principal assigned to the Azure Kubernetes Cluster. If you want, you can go ahead and echo the client ID. So we have the client ID in place. Now let's go ahead and get the Azure Container Store ID. That is also done. Now we'll go ahead and assign a role. So we'll ensure that the service principal has the role of an ACR pool. So that is the pulling of images from the Azure Container Registry.

33. AZ-203 - Application deployment files

Now let's go over the deployment files which are going to be used to deploy our application onto our cluster. So these are basically Yammer files. So Yammer files are used as a specification, normally for configuration files. So the Yammer files have a structure, and again, it consists of mostly key value pairs. So first I'm going to mention what the first thing we're going to be doing as part of this YAML file. So we want to create a deployment. The deployment would consist of a pod. So we're going to give a name to our deployment. As I mentioned, for a particular pod running your container. There are numerous pod replicas to choose from. For the purpose of the demo, I'll keep it simple with just one replica. I will then give a name for ourapplication which needs to run as part of the pod. Now, if I just scroll a little bit down, as part of my pod deployment, I am going to mention what the container that I want to run as part of the sport is. Now I'm going to make sure that I pick up the image format as your container registry. And I'm going to make sure that I have the port mentioned has port 80. So, what will this YAML file do? When we submit this configuration file to our cluster, the query software will actually understand each line of this deployment file. It will then pick up this image from the Azure Container Registry. It will then create a container out of that image. It will then run the container in a pod and will create a pod as part of a deployment. It will give a name to the pod and it will give a name to the deployment. So this forms the deployment of the pod on the cluster. I have another YAML file, which is a service file. Now, I want to expose this deployment so that I can actually reach out to this deployment from the outside world. So I can expose it as a service using the type of load balancer. Again, I just give the name of the service and expose the port. I want to make sure that I give the name of the port that I want to expose as part of the service. So now let's go ahead and actually deploy our application onto our cluster using these YAML files.

34. AZ-203 - Lab - Deploying the application onto the Kubernetes cluster

Now I want to go ahead and deploy our application to our cluster using the YAML files we saw earlier. Now, currently, those YAML files are on my local system. In order to make sure that it's available in Cloudshell, you can go ahead and click on Upload, and then browse for those files on your local machine. Now, once the file files are in place, I'll issue the cubesql apply command to apply our application YAML file. So now that we've deployed our application,we can use the cubesatl command and getall command to see what the status is. So now we can currently see we have one pod running. It's in the running state. We have our demo app deployment also in the running state, and it's available. We also have our demo app deployment in place. Now, let's go ahead and apply our service file. Our service YAML file. So the service is also in place. If I use the cubes, it will get all the commands. I can now see that a new service is in place. Now, currently, the external IPis are in the pending state. After some time, if you again issue the CubeCDL, get all command, you can now see that an external IP has been assigned to the Demo app service. So let's go ahead and browse the external IP in a new tab. And now you can see your net containerized application running. And now it's running as part of your Kubernetes cluster, right? So this marks the end of this chapter in which we have seen how we could deploy an application onto a Kubernetes cluster.

Develop Azure Platform as a Service compute solutions

1. AZ-203/204 - Azure Web App Service

Hi and welcome back. Now in this chapter, I want to talk about the Azure Web App service. So this is part of an Azure Appservice that's available on the Azure platform. Now, what's the entire purpose of the Azure Web App service? So let's say you want to deploy an application onto Azure. So let's say this is a web application that needs to be accessed by your users. Now, one of the options for deploying the web application is to probably spin up a virtual machine, or probably a set of virtual machines, and install your web server. So it could be Internet Information Services if you have a DotNet-based application, and then you go ahead and deploy your web application onto this virtual machine. Now, in such a scenario, what are you responsible for? So obviously, you are responsible for the maintenance of the virtual machine. So you have to ensure that you carry out the necessary security, patching, etc. What Azure is offering is that they are offering something known as a platform as a service. So it's a past offering. The platform has a service which is known as the Azure Web App service. So what you can do is that now you can actually deploy your web application onto this appservice instead of deploying it onto a virtual machine. And what the service does is that the underlying infrastructure is managed for you. So you have to think about the virtual machines that are hosting your web application. That's all done in the background for you. And there are many more features that are available. When you look at the Azure Web App service, for example, there is a feature known as deployment slots. So, with the advantage of deployment slots, what happens is that you can actually create kind of two versions of your web applications. So one could be your stage, one could be your production. So this is good when you want to have a blue grain deployment scenario. So currently you have users who are accessing your production-based application. What you can do is that you can then deploy a more recent version of your application onto the same Azure Web App service, onto something known as a "staging slot," so you can create another slot. So, this is like another web application running on your Azure App service. It gets a different URL. Your users can then have your test users cantest the application in the staging slot. And if everything is fine, you can make a quick switch over from staging to production. So, your staging application will automatically switch over to your production application. Just one advantage. There are other advantages, like having backups, having SSL, having custom domains mapped to your Azure App service. So there are features if you go ahead and choose the Azure Web App service, right? So this marks the end of this chapter in which we have looked at an introduction to the Azure Web app service.

2. AZ-203/204 - Azure App Service Plan

Hi and welcome back. Now in this chapter, I am going to talk about app service plans. Now, when you deploy a web application onto an Azure web app service, when you create that Azureweb App service resource itself, you also have to create something known as an App service plan resource. So these are both linked together. The app service plan will actually determine how much you will pay per month for using that as your web app service. Now, there are different types of app service plans,so these are different tiers that are available. Please note that this is very important to understand what the different features are available for the different apps or plans. So I mentioned that when you create an as your webapp resource, you also have to create an as your appservice plan resource, and there is a cost that is linked to each one of these app service plans. So let's quickly go through some of the key features when it comes to the different app service plans. Now you have the free app service plan. So, as the name does denote, you don't pay anything for this app service plan. So, as part of this plan, you can deploy ten applications and you get one GB of disc space. Now, the issue that you have, or let's say the limitation that you have with this app service plan, is that you only get 60 minutes of compute time per day. So that means if you host, let's say, two web applications to Azure web apps as part of this app service plan, if we combine the running time of both of these applications, it will stop running. So you are limited to only running your apps as part of this app service plan for a collective time of only 60 minutes. As a result, this is a significant limitation. Next, you have the shared app service plan. where you do pay a small amount. But again, in this, there is a limitation where you now get only 240 minutes of running time per day. So there are the free and the shared. Now we'll go on to the basics. You don't have any limitations such as these for the runtime of your web apps because now what is happening is that in the basic app service plan, the infrastructure will actually start creating virtual machines for you to host your web applications. In the case of the free and shared app service plans, your web app is taken onto any shared infrastructure. So you don't have virtual machines allocated to you for hosting the web applications. However, in the basic App service plan, I stated that you have virtual machines assigned to you for hosting your web application. That is why there is no limitation on the amount of time that you can run your web application. so it can run throughout the entire day. In this, what you get now is a max number of instances. So over here you can go up to three. So what happens is that you remember that you have an unlimited number of applications which can be deployed using this web service. So let's say in the beginning you have one virtual machine that's launched as part of your app service plan. You start putting in, let's say, two applications, three applications. And remember, this is a virtual machine, so it has its limitations. So now let's say that the virtual machine is having performance issues because you are hosting more and more web applications. Because you might want to do that to make full use of the price you're paying for the basic app service plan. In such a case, what you can do is start upscaling or launching new virtual machines as part of your app service plan so that your webapplications start getting distributed across the virtual machines. In this case, you have a limit of three. So you can spin up a total of three virtual machines for hosting your web applications. So, even though you have an unlimited number of web applications that you can deploy, obviously this will be limited by your capacity. So you have three virtual machines that can host your web applications. As part of the basic app service plan, you also start getting an SLA. So you are guaranteed that your web application will run 99.95% of the time. Now, please remember that when you start getting virtual machines as part of your app service plan, you will also get billed for the running cost of your virtual machine. So all of that now becomes a combinedpackage and that's what you're going to pay per month for the app service plan. And as you start going down the line, you can see that you get more space, you get a greater number of instances. And with the standard app service plan, there are also some additional benefits which will just go through. So there's a long list of features that are available for the app service plans. And then you have an app service plan that is available for Linux, and then you have a plan that is available for Azure functions. Now let's scroll down. So as we go down, you can see that we have now come onto the app deployment section. Now, what is very important, which I want to point out, has a lot of features. Let's focus on the main ones. We have something known as "deployment slots." So remember, in the Azure Web App chapter, we talked a little bit about deployment slots. This deployment slot feature is only available with the standard app service plan and beyond. So it's not available with the basic. So, if you want to have an abluegreen deployment, you must select the standard app service plan. If you want to host Docker-based containers, then you should go for the Linux App service plan. Let's scroll down. What else is important? So if you go on to the networking section,if you look at hybrid connection, that's connecting your Azure Web App with your on-premise infrastructure. So that's available for all of the app service plans. When you look at it, we need it integrated. So let's say you want to integrate your Azure Web App with your Azure virtual network. Again, it's only available from the standard App service plan and beyond. Now, in the Azure App service or your Azure Web applications, please don't restrict yourself to just a net programming language. So here you can see that you can deploy a lot of applications, different types of applications. Utilizing the Azure web service You have a net. You have Java, Node, JS, PHP, Python, and Ruby. Now, apart from that, a very important feature is auto scaling. So we'll go through auto scaling a little bit later on. Again, auto scaling is only available with the standard App service plan or higher. And then if you again scroll down, you have important things like backup restore, custom domain, so you can attach your own customdomain to your Azure App service. And that's available with the shared plan itself. If you want to enable SSL, that's another important thing. So if you look at SSL over here, it's available from the basic App service plan or higher. So this table is very important when it comes to app service plans and determining which app service plan is best for your Azure devops service. Right, so this marks the end of this chapter.

ExamSnap's Microsoft AZ-204 Practice Test Questions and Exam Dumps, study guide, and video training course are complicated in premium bundle. The Exam Updated are monitored by Industry Leading IT Trainers with over 15 years of experience, Microsoft AZ-204 Exam Dumps and Practice Test Questions cover all the Exam Objectives to make sure you pass your exam easily.