[Build and Deploy Staging Site] Publish from microsoft/azuretipsandtricks-private:main/src/blog
This commit is contained in:
Родитель
47555cc3d2
Коммит
b65b2ec71d
|
@ -22,7 +22,7 @@ This post was brought to you by **[Kumar Allamraju](https://twitter.com/kumarall
|
|||
|
||||
Recently I was engaged to help on customer's issue in which their [Azure Network Load Balancer](https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-overview/?WT.mc_id=docs-azuredevtips-azureappsdev) is unable to reach their backend instances because the load balancer declared them as unhealthy. However they can directly reach the backend instances and able to execute the application but unable to reach the same via Azure NLB.
|
||||
|
||||
## Analysis
|
||||
#### Analysis
|
||||
|
||||
The first thing I did was to check their load balancer's health probes. However they are using "Basic Load Balancer" and the health probes are only available in the standard tier. I end up working with my Cloud Ops/Support team to see what's going on for this customer's load balancer. Further investigation revealed that customer's Network Security Group (NSG), with a rule named ‘defaultdenyinbound’ is not accepting any traffic other than their VNet IP's. Due to this rule, NLB was unable to send probes to backend instances. I recommended the customer to make the following changes
|
||||
|
||||
|
@ -39,7 +39,7 @@ The public IP address 168.63.129.16 is used in all Azure public regions and all
|
|||
Azure Load Balancer probes originates from this IP address. If customer's block this IP address, their probes will fail leading to the above situation. The customer is convinced with the above explanation. After allowing this IP in their local firewall policies, they are able to reach the backend instances via Azure NLB and the problem is solved.
|
||||
|
||||
|
||||
## References
|
||||
#### References
|
||||
|
||||
* [What is IP address 168.63.129.16?](https://docs.microsoft.com/en-us/azure/virtual-network/what-is-ip-address-168-63-129-16?WT.mc_id=docs-azuredevtips-azureappsdev)
|
||||
|
||||
|
|
|
@ -27,7 +27,7 @@ If you are new to Azure or if you want to run an experiment on Azure, you can us
|
|||
|
||||
In this post, we'll explore how to create an Azure account that you can for free, and what's included in the offer.
|
||||
|
||||
## Creating a free Azure account
|
||||
#### Creating a free Azure account
|
||||
|
||||
To start your journey into Azure, you can go to [https://azure.microsoft.com/free/](https://azure.microsoft.com/free/?WT.mc_id=azure-azuredevtips-azureappsdev). This takes you to the landing page of the free account offer, which looks like this:
|
||||
|
||||
|
@ -104,7 +104,7 @@ Let's create a free account!
|
|||
|
||||
After a few moments, you Azure subscription is ready. Now, you can go to the Azure portal ([https://portal.azure.com/](https://portal.azure.com/?WT.mc_id=azure-azuredevtips-azureappsdev)) and start using Azure.
|
||||
|
||||
## Start using Azure
|
||||
#### Start using Azure
|
||||
|
||||
Now that you have a free account, you can start using Azure.
|
||||
|
||||
|
@ -130,7 +130,7 @@ You can also use one of the services that has a free tier. You can try that with
|
|||
|
||||
(Web Apps free tier in the Azure portal)
|
||||
|
||||
## Monitor your free usage
|
||||
#### Monitor your free usage
|
||||
|
||||
In the Azure portal, you can see the usage of your free services when you look at your subscription details:
|
||||
1. Go to the [Azure portal](https://portal.azure.com/?WT.mc_id=azure-azuredevtips-azureappsdev)
|
||||
|
@ -143,6 +143,6 @@ You'll now see your usage for the free services, shown in percentage. Here, you'
|
|||
|
||||
(Free service usage in the Azure portal)
|
||||
|
||||
## Conclusion
|
||||
#### Conclusion
|
||||
|
||||
If you want to try Azure for free, you can! There are many services that you can use for free, for 12 months. On top of that, you get \$200 to spend in the first month. And there are many services that always have a free usage tier, so that you can use them for free, or just try them out. [Sign up now](https://azure.microsoft.com/free/?WT.mc_id=azure-azuredevtips-azureappsdev) and check it out!
|
||||
|
|
|
@ -25,20 +25,20 @@ date: 2020-02-27 02:00:00
|
|||
|
||||
With **GitHub Actions** you can build end-to-end continuous integration (CI) and continuous deployment (CD) capabilities directly in your repository.
|
||||
|
||||
### What’s covered in this lab
|
||||
#### What’s covered in this lab
|
||||
|
||||
In this lab, you will:
|
||||
|
||||
1. Create a web app on Azure using the App Service extension
|
||||
2. Create a workflow with GitHub Actions to add CI/CD to your app
|
||||
|
||||
### Prerequisites
|
||||
#### Prerequisites
|
||||
|
||||
1. Your Windows machine should have Node.js LTS and Visual Studio Code.
|
||||
|
||||
2. You are using a GitHub account and an Azure account made for the purposes of this lab. These have been already logged into from your machine and the account info is saved.
|
||||
|
||||
### Setting up the GitHub repo
|
||||
#### Setting up the GitHub repo
|
||||
|
||||
1. Navigate to the [example app repository](https://github.com/fiveisprime/Useful-Website?WT.mc_id=github-azuredevtips-azureappsdev).
|
||||
|
||||
|
@ -46,7 +46,7 @@ In this lab, you will:
|
|||
|
||||
<img :src="$withBase('/files/fork-github.png')">
|
||||
|
||||
## Create an Azure App Service web app
|
||||
#### Create an Azure App Service web app
|
||||
|
||||
Create the App Service web app that you'l deploy to from GitHub.
|
||||
|
||||
|
@ -70,7 +70,7 @@ Create the App Service web app that you'l deploy to from GitHub.
|
|||
|
||||
<img :src="$withBase('/files/python-default-site.png')">
|
||||
|
||||
## Set up CI/CD with GitHub Actions
|
||||
#### Set up CI/CD with GitHub Actions
|
||||
|
||||
Use GitHub actions to automate the deployment workflow for this web app.
|
||||
|
||||
|
@ -157,7 +157,7 @@ Use GitHub actions to automate the deployment workflow for this web app.
|
|||
|
||||
<img :src="$withBase('/files/workflow-complete.png')">
|
||||
|
||||
## Test out your app!
|
||||
#### Test out your app!
|
||||
|
||||
1. Back in VS Code, go to the App Service extension, and right click on your app service and click on "Browse Website" to see your site running.
|
||||
|
||||
|
@ -172,7 +172,7 @@ Use GitHub actions to automate the deployment workflow for this web app.
|
|||
|
||||
1) Go back to the Actions tab and you can watch the build finishing up. Once you see all the green check marks, go to Edge and reload your website!
|
||||
|
||||
## Live streaming software development
|
||||
#### Live streaming software development
|
||||
|
||||
On a side note - If you like Azure Tips and Tricks, then you might enjoy another project that I'm working on for live streaming. Check out my channel below and hit the follow button to know when I'm live.
|
||||
|
||||
|
|
Загрузка…
Ссылка в новой задаче