Application Gateway Configuration Step by Step | Azure App Gateway Tutorial
ฝัง
- เผยแพร่เมื่อ 25 ก.ค. 2024
- Azure Application Gateway is a web traffic load balancer that enables you to manage traffic to your web applications. Traditional load balancers operate at the transport layer (OSI layer 4 - TCP and UDP) and route traffic based on source IP address and port, to a destination IP address and port.
00:00 Intro
00:47 Architecture of the Demo?
01:34 What is Azure Application Gateway?
03:10 Configuring the Resources for Demo
04:41 Application Gateway Configuration
11:52 Troubleshooting :)
13:08 How it Works
13:49 Outro
Application Gateway can make routing decisions based on additional attributes of an HTTP request, for example URI path or host headers.
docs.microsoft.com/en-us/azur...
Code Sample - gist.github.com/KamalRathnaya...
Meet Kamal Today!
Kamal Rathnayake
very straight forward thanks
nice tutorial thanks
This is incredibly helpful. I have to transition from AWS to Azure. Thank you!
Doing exactly the same :D New adventure :DDD
Hey, thank you for making this video, Kamal, this is quite helpful, Hope you continue to do this! 🙌
Can you please do a video on integrate Application Gateway with NGINIX ingress controller for Azure Kubernetes Service
So one thing that seems really strange to me is that during the Routing Rule creation, you say the target type is backend pool and then on the next line you select ImageServers. This makes me think that all requests for this rule should go to ImageServers yet under the Path based rules section, you send requests to both ImageServers and VideoServers. This is really confusing to me. Why do they require us to specify the backend target at the Routing Rule level if you have to specify the backend target on the path based section? Maybe the path based section is optional so you need the default back end target to be specified at the rule level. Don't know but it is typical Microsoft crappy documentation in their UI
Okol r