Merge branch 'Azure:main' into main

README.md

@@ -1,6 +1,6 @@
 # AKS Landing Zone Accelerator
 
-Azure Landing Zone Accelerators are an architectural approach and a reference implementation that enables effective construction and operationalization of landing zones on Azure, at scale. This approach aligns with the Azure roadmap and the Cloud Adoption Framework for Azure.
+Azure Landing Zone Accelerators are architectural guidance, reference architecture, reference implementations and automation packaged to deploy workload platforms on Azure at Scale and aligned with industry proven practices.
 
 AKS Landing Zone Accelerator represents the strategic design path and target technical state for an Azure Kubernetes Service (AKS) deployment. This solution provides an architectural approach and reference implementation to prepare landing zone subscriptions for a scalable Azure Kubernetes Service (AKS) cluster. For the architectural guidance, check out [AKS Landing Zone Accelerator](https://docs.microsoft.com/azure/cloud-adoption-framework/scenarios/aks/enterprise-scale-landing-zone) in Microsoft Docs. 
 

Scenarios/AKS-Secure-Baseline-PrivateCluster/Bicep/README.md

@@ -1,12 +1,4 @@
-# Enterprise Scale for AKS - Private Cluster Scenario
-
-## Steps of Implementation for AKS Construction Set
-
-A deployment of AKS-hosted workloads typically experiences a separation of duties and lifecycle management in the area of prerequisites, the host network, the cluster infrastructure, and finally the workload itself. This reference implementation is similar. Also, be aware our primary purpose is to illustrate the topology and decisions of a baseline cluster. We feel a "step-by-step" flow will help you learn the pieces of the solution and give you insight into the relationship between them. Ultimately, lifecycle/SDLC management of your cluster and its dependencies will depend on your situation (team roles, organizational standards, tooling, etc), and must be implemented as appropriate for your needs.
-
-## Accounting for Separation of Duties
-
-While the code here is located in one folder in a single repo, the steps are designed to mimic how an organization may break up the deployment of various Azure components across teams, into different code repos or have them run by different pipelines with specific credentials.
+# AKS landing zone accelerator - Private Cluster Scenario for Bicep
 
 ## Keeping It As Simple As Possible
 

Scenarios/AKS-Secure-Baseline-PrivateCluster/README.md

@@ -8,7 +8,7 @@ When using a private cluster, the control plane can only be accessed from comput
 
 By the end of this, you would have deployed a secure AKS cluster, complient with Enterprise-Scale for AKS guidance and best practices. We will also be deploying a workload known as the Ratings app that is also featured in the [Azure Kubernetes Services Workshop](https://docs.microsoft.com/en-us/learn/modules/aks-workshop/). Check out the workshop for some intermediate level training on AKS.
 
-For this scenario, we have various IaC technology that you can choose from depending on your preference. At this time only the ARM version is available. Below is an architectural diagram of this scenario.
+For this scenario, we have various IaC technology that you can choose from depending on your preference. At this time only the Terraform and Bicep versions are available. Below is an architectural diagram of this scenario.
 
 ![Architectural diagram for the secure baseline scenario.](./media/AKS-private-cluster-scenario.jpg)
 
@@ -40,15 +40,9 @@ For this scenario, we have various IaC technology that you can choose from depen
 * Azure MongoDb
 * Azure Redis Cache
 
-## Steps of Implementation for AKS Construction Set
-
-A deployment of AKS-hosted workloads typically experiences a separation of duties and lifecycle management in the area of prerequisites, the host network, the cluster infrastructure, and finally the workload itself. This reference implementation is similar. Also, be aware our primary purpose is to illustrate the topology and decisions of a baseline cluster. We feel a "step-by-step" flow will help you learn the pieces of the solution and give you insight into the relationship between them. Ultimately, lifecycle/SDLC management of your cluster and its dependencies will depend on your situation (team roles, organizational standards, etc), and will be implemented as appropriate for your needs.
-
 ## Next
 Pick one of the IaC options below and follow the instructions to deploy the AKS reference implementation.
 
-:arrow_forward: [ARM](./ARM)(Depricated)
-
 :arrow_forward: [Terraform](./Terraform)
 
 :arrow_forward: [Bicep](./Bicep)