Hugging Face's logo

Spaces:
awacke1
/
AzureContainerAppsAIArchitecture
Runtime error

App Files Community
AzureContainerAppsAIArchitecture
File size: 4,390 Bytes 
ae53587
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
 

# Azure Container Apps
1. 👥 Users
   - 📥 Inbound Traffic

2. 🌐 Load Balancer w Public IP
   - 🕸️ Virtual Network
   - 🔒 Private Endpoints
   - 📦 External Container App env w Ingress IP restrictions

3. 🔒 Private Endpoints
   - 🗝️ Key Vault
   - 🛢️ Container Registry
   - 🚀 Cache for REDIS
   - 💾 Storage
   - 🚍 Service Bus

4. 📤 Outbound Traffic
   - 🔥 Firewall
   - 🗺️ Route Table


## 🌐 Azure Container Apps - Outline
1. 📦 Container Apps Overview
	- 🌟 ACA is serverless microservices mashup of Open Source:
		1. 🐳 Kubernetes: Container
		2. 🚀 Dapr: Runtime and API
		3. 📈 KEDA: Kube based autoscaler
		4. 🛡️ Envoy: Proxy w Endpoint SSL
	- 🔍 Service Discovery
	- 🚦 Traffic Splitting
	- 📊 Event driven scaling based on traffic
	- 📮 Event source queues
	- ⬇️ Scales down to zero
	- 🔄 Long running processes and background tasks
2. 🌍 Environment Internal vs External
	- 🌐 External: Public VIP
	- 🔒 Internal: VIP and ILB
3. 🏗️ Infrastructure w/ Azure Bicep
4. ⚖️ Load Balancing Options




# 🌐 Azure Bicep vs 🏗️ HashiCorp Terraform

## Overview
- Azure Bicep
  - 🎯 Domain-specific language (DSL) for deploying Azure resources
  - 💼 Developed and maintained by Microsoft
  - 🌐 Azure-centric; specifically designed for Azure Resource Manager (ARM) templates
- HashiCorp Terraform
  - 🎯 Open-source infrastructure as code (IaC) tool
  - 💼 Developed and maintained by HashiCorp
  - 🏢 Multi-cloud and multi-provider support

## Language and Syntax
- Azure Bicep
  - 📝 Easier, simplified syntax compared to ARM templates
  - 🚀 Transpiles to ARM templates
- HashiCorp Terraform
  - 📝 HashiCorp Configuration Language (HCL); more complex syntax than Bicep
  - 🗂️ Uses provider-specific resource definitions

## Provider Support
- Azure Bicep
  - 🔒 Limited to Azure services and resources
- HashiCorp Terraform
  - 🌩️ Supports multiple cloud providers (e.g., AWS, GCP, Azure) and non-cloud services
  - 📦 Extensible through custom providers

## Community and Ecosystem
- Azure Bicep
  - 🌱 Growing community focused on Azure resources
  - 📚 Limited to Azure documentation and resources
- HashiCorp Terraform
  - 🌳 Mature and established community and ecosystem
  - 📚 Extensive documentation and resources for various cloud providers and platforms

## Conclusion
- Azure Bicep is best suited for organizations and developers primarily focused on Azure resources with a need for a simple, Azure-centric IaC solution.
- 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.


# 📥 Ingress vs Egress

1. 📥 Ingress
   - 🌐 External Traffic
      - Incoming traffic from users, clients, or other services outside the network
      - Accessing resources within the network or system (e.g., API, web services)
   - 🔒 Internal Traffic
      - Communication between components within the network or system (e.g., microservices)
      - Typically restricted access for improved security

2. 📤 Egress
   - 🌐 External Traffic
      - Outgoing traffic from the network or system to users, clients, or other services
      - Sending responses or data to external entities
   - 🔒 Internal Traffic
      - Communication between components within the network or system (e.g., microservices)
      - Typically restricted access for improved security
    
For Ingress: Azure Container Apps supports HTTPS and TCP types of ingress.

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.

FrontDoor app delivery net provides global load balanceand site acceleration similar to L7.  Available in Std and Premium.




# Terraform Import:

![image](https://user-images.githubusercontent.com/30595158/231140616-a6089091-e195-451a-95e5-54ea3c94fe80.png)

Usage: terraform import ADDR ID


# Azure Container Registry
Admin user - enable to access via CLI

Name and Resource Group
Location (Central) - 

# Github Actions YAML:

1. Azure Build Docker Image, Push ACR
2. Azure Container App Deploy
3. Dockerfile (Image Push)