Spaces:
Runtime error
Runtime error
Create app.py
Browse files
app.py
ADDED
|
@@ -0,0 +1,130 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
|
| 2 |
+
# Azure Container Apps
|
| 3 |
+
1. 👥 Users
|
| 4 |
+
- 📥 Inbound Traffic
|
| 5 |
+
|
| 6 |
+
2. 🌐 Load Balancer w Public IP
|
| 7 |
+
- 🕸️ Virtual Network
|
| 8 |
+
- 🔒 Private Endpoints
|
| 9 |
+
- 📦 External Container App env w Ingress IP restrictions
|
| 10 |
+
|
| 11 |
+
3. 🔒 Private Endpoints
|
| 12 |
+
- 🗝️ Key Vault
|
| 13 |
+
- 🛢️ Container Registry
|
| 14 |
+
- 🚀 Cache for REDIS
|
| 15 |
+
- 💾 Storage
|
| 16 |
+
- 🚍 Service Bus
|
| 17 |
+
|
| 18 |
+
4. 📤 Outbound Traffic
|
| 19 |
+
- 🔥 Firewall
|
| 20 |
+
- 🗺️ Route Table
|
| 21 |
+
|
| 22 |
+
|
| 23 |
+
## 🌐 Azure Container Apps - Outline
|
| 24 |
+
1. 📦 Container Apps Overview
|
| 25 |
+
- 🌟 ACA is serverless microservices mashup of Open Source:
|
| 26 |
+
1. 🐳 Kubernetes: Container
|
| 27 |
+
2. 🚀 Dapr: Runtime and API
|
| 28 |
+
3. 📈 KEDA: Kube based autoscaler
|
| 29 |
+
4. 🛡️ Envoy: Proxy w Endpoint SSL
|
| 30 |
+
- 🔍 Service Discovery
|
| 31 |
+
- 🚦 Traffic Splitting
|
| 32 |
+
- 📊 Event driven scaling based on traffic
|
| 33 |
+
- 📮 Event source queues
|
| 34 |
+
- ⬇️ Scales down to zero
|
| 35 |
+
- 🔄 Long running processes and background tasks
|
| 36 |
+
2. 🌍 Environment Internal vs External
|
| 37 |
+
- 🌐 External: Public VIP
|
| 38 |
+
- 🔒 Internal: VIP and ILB
|
| 39 |
+
3. 🏗️ Infrastructure w/ Azure Bicep
|
| 40 |
+
4. ⚖️ Load Balancing Options
|
| 41 |
+
|
| 42 |
+
|
| 43 |
+
|
| 44 |
+
|
| 45 |
+
# 🌐 Azure Bicep vs 🏗️ HashiCorp Terraform
|
| 46 |
+
|
| 47 |
+
## Overview
|
| 48 |
+
- Azure Bicep
|
| 49 |
+
- 🎯 Domain-specific language (DSL) for deploying Azure resources
|
| 50 |
+
- 💼 Developed and maintained by Microsoft
|
| 51 |
+
- 🌐 Azure-centric; specifically designed for Azure Resource Manager (ARM) templates
|
| 52 |
+
- HashiCorp Terraform
|
| 53 |
+
- 🎯 Open-source infrastructure as code (IaC) tool
|
| 54 |
+
- 💼 Developed and maintained by HashiCorp
|
| 55 |
+
- 🏢 Multi-cloud and multi-provider support
|
| 56 |
+
|
| 57 |
+
## Language and Syntax
|
| 58 |
+
- Azure Bicep
|
| 59 |
+
- 📝 Easier, simplified syntax compared to ARM templates
|
| 60 |
+
- 🚀 Transpiles to ARM templates
|
| 61 |
+
- HashiCorp Terraform
|
| 62 |
+
- 📝 HashiCorp Configuration Language (HCL); more complex syntax than Bicep
|
| 63 |
+
- 🗂️ Uses provider-specific resource definitions
|
| 64 |
+
|
| 65 |
+
## Provider Support
|
| 66 |
+
- Azure Bicep
|
| 67 |
+
- 🔒 Limited to Azure services and resources
|
| 68 |
+
- HashiCorp Terraform
|
| 69 |
+
- 🌩️ Supports multiple cloud providers (e.g., AWS, GCP, Azure) and non-cloud services
|
| 70 |
+
- 📦 Extensible through custom providers
|
| 71 |
+
|
| 72 |
+
## Community and Ecosystem
|
| 73 |
+
- Azure Bicep
|
| 74 |
+
- 🌱 Growing community focused on Azure resources
|
| 75 |
+
- 📚 Limited to Azure documentation and resources
|
| 76 |
+
- HashiCorp Terraform
|
| 77 |
+
- 🌳 Mature and established community and ecosystem
|
| 78 |
+
- 📚 Extensive documentation and resources for various cloud providers and platforms
|
| 79 |
+
|
| 80 |
+
## Conclusion
|
| 81 |
+
- Azure Bicep is best suited for organizations and developers primarily focused on Azure resources with a need for a simple, Azure-centric IaC solution.
|
| 82 |
+
- HashiCorp Terraform is ideal for organizations and developers with multi-cloud or multi-provider requirements, as it offers greater flexibility and extensibility across different platforms.
|
| 83 |
+
|
| 84 |
+
|
| 85 |
+
# 📥 Ingress vs Egress
|
| 86 |
+
|
| 87 |
+
1. 📥 Ingress
|
| 88 |
+
- 🌐 External Traffic
|
| 89 |
+
- Incoming traffic from users, clients, or other services outside the network
|
| 90 |
+
- Accessing resources within the network or system (e.g., API, web services)
|
| 91 |
+
- 🔒 Internal Traffic
|
| 92 |
+
- Communication between components within the network or system (e.g., microservices)
|
| 93 |
+
- Typically restricted access for improved security
|
| 94 |
+
|
| 95 |
+
2. 📤 Egress
|
| 96 |
+
- 🌐 External Traffic
|
| 97 |
+
- Outgoing traffic from the network or system to users, clients, or other services
|
| 98 |
+
- Sending responses or data to external entities
|
| 99 |
+
- 🔒 Internal Traffic
|
| 100 |
+
- Communication between components within the network or system (e.g., microservices)
|
| 101 |
+
- Typically restricted access for improved security
|
| 102 |
+
|
| 103 |
+
For Ingress: Azure Container Apps supports HTTPS and TCP types of ingress.
|
| 104 |
+
|
| 105 |
+
With HTTPS ingress enabled container apps support TLS, HTTP/1.1 and 2, Websocket, gRPC. TLS1.2 is used for HTTPS. Endpoints expose port 80, 443. 80 is redirected to 443. App accessed on FQDN. Request timeout is 240 seconds.
|
| 106 |
+
|
| 107 |
+
FrontDoor app delivery net provides global load balanceand site acceleration similar to L7. Available in Std and Premium.
|
| 108 |
+
|
| 109 |
+
|
| 110 |
+
|
| 111 |
+
|
| 112 |
+
# Terraform Import:
|
| 113 |
+
|
| 114 |
+
|
| 115 |
+
|
| 116 |
+
Usage: terraform import ADDR ID
|
| 117 |
+
|
| 118 |
+
|
| 119 |
+
# Azure Container Registry
|
| 120 |
+
Admin user - enable to access via CLI
|
| 121 |
+
|
| 122 |
+
Name and Resource Group
|
| 123 |
+
Location (Central) -
|
| 124 |
+
|
| 125 |
+
# Github Actions YAML:
|
| 126 |
+
|
| 127 |
+
1. Azure Build Docker Image, Push ACR
|
| 128 |
+
2. Azure Container App Deploy
|
| 129 |
+
3. Dockerfile (Image Push)
|
| 130 |
+
|