Skip to content

Commit

Permalink
docs: update docs for aca-revisions and aca-store
Browse files Browse the repository at this point in the history
Signed-off-by: Kristina Devochko <[email protected]>
  • Loading branch information
guidemetothemoon committed Apr 1, 2024
1 parent 95b1e29 commit 29edc4e
Show file tree
Hide file tree
Showing 2 changed files with 16 additions and 10 deletions.
6 changes: 6 additions & 0 deletions aca-revision-and-traffic-management/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,12 @@

This folder contains Bicep code for provisioning a demo application that can be used to see multiple revisions and traffic splitting for Azure Container Apps in action. Demo application itself is a simple Hello World application that was initially created by Microsoft for AKS demos, but why not re-use it for Azure Container Apps as well? 😼

Implementation includes following modules:

* [common](modules/common.bicep): includes common, shared resources that are used by other resources in the deployment. For example, managed identities or deployment-specific Azure Policy assignments.
* [aca_common](modules/aca-common.bicep): includes resources that are common for Azure Container Apps, like Azure Container Apps environment.
* [public_apps](modules/aca-public-apps.bicep): includes container apps that are publicly accessible.

## Deployment instructions

1. Deploy code as-is first (after adjusting parameters as per your use case) - initially in [aca-public-apps.bicep](modules/aca-public-apps.bicep) it's defined that application will be deployed in multi-revision mode, but when we start from nothing only one, first, revision will be deployed. Due to that in ```*.bicepparam``` file traffic distribution is configured to send 100% traffic to the latest revision, which will be the app's very first revision.
Expand Down
20 changes: 10 additions & 10 deletions aks-store-on-aca/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,16 +8,16 @@ Below you may find the Azure solution architecture diagram:

Implementation includes following modules:

* ```common```: includes common, shared resources that are used by other resources in the deployment. For example, managed identities or deployment-specific Azure Policy assignments.
* ```network```: includes network-related resources. For example, virtual networks, subnets and network security groups.
* ```dns```: includes DNS-related resources. For example, private DNS zones.
* ```vnet_links```: includes virtual network link resources for mapping of virtual networks with private DNS zones, which is required for the private endpoints to function properly.
* ```kv```: includes Azure Key Vault resources, with enabled RBAC and configuration for secure access to the resources with private endpoints.
* ```azure_monitor```: includes observability-related resources, like Log Analytics, Application Insights, etc. It also includes Azure Monitor Private Link Scope (AMPLS) and related resources for configuration of secure access to Azure Monitor services.
* ```ai```: includes cognitive services, like Azure OpenAI with respective model deployments and configuration for secure access to the resources with private endpoints.
* ```aca_common```: includes resources that are common for Azure Container Apps, like Azure Container Apps environment and network configuration for secure communication to and between apps.
* ```internal_apps```: includes container apps that are not publicly accessible, i.e. internal services.
* ```public_apps```: includes container apps that are publicly accessible.
* [common](modules/common.bicep): includes common, shared resources that are used by other resources in the deployment. For example, managed identities or deployment-specific Azure Policy assignments.
* [network](modules/network.bicep): includes network-related resources. For example, virtual networks, subnets and network security groups.
* [dns](modules/dns.bicep): includes DNS-related resources. For example, private DNS zones.
* [vnet_links](modules/virtual-network-links.bicep): includes virtual network link resources for mapping of virtual networks with private DNS zones, which is required for the private endpoints to function properly.
* [kv](modules/keyvault.bicep): includes Azure Key Vault resources, with enabled RBAC and configuration for secure access to the resources with private endpoints.
* [azure_monitor](modules/azure-monitor.bicep): includes observability-related resources, like Log Analytics, Application Insights, etc. It also includes Azure Monitor Private Link Scope (AMPLS) and related resources for configuration of secure access to Azure Monitor services.
* [ai](modules/ai.bicep): includes cognitive services, like Azure OpenAI with respective model deployments and configuration for secure access to the resources with private endpoints.
* [aca_common](modules/aca-common.bicep): includes resources that are common for Azure Container Apps, like Azure Container Apps environment and network configuration for secure communication to and between apps.
* [internal_apps](modules/aca-internal-apps.bicep): includes container apps that are not publicly accessible, i.e. internal services.
* [public_apps](modules/aca-public-apps.bicep): includes container apps that are publicly accessible.

## Deployment instructions

Expand Down

0 comments on commit 29edc4e

Please sign in to comment.