d4b2b49b57
* add wrapper bicep file * update pipeline * fix nsg typo * update dependency * update dependency * default kube version * update resourcegroup name * update pipeline * update kv script * moving hardcoded values into parameter file * remove certificates from param file * adding parameter file into pipeline * remove default values --------- Co-authored-by: Ayobami Ayodeji <ayobaami@hotmail.com> Co-authored-by: Rainer Halanek <rahalan@microsoft.com> Co-authored-by: Rainer Halanek <61878316+rahalan@users.noreply.github.com> |
||
---|---|---|
.. | ||
App-AzureVote-BuildOnACR.yml | ||
App-AzureVote-HelmRunCmd-LegacyAuth.yml | ||
App-AzureVote-HelmRunCmd.yml | ||
App-Flask-DockerBuild.yml | ||
App-Flask-GitOps.yml | ||
App-Sec-Deploy-Flask-DockerBuild.yml | ||
App-Test-All.yml | ||
Check-Markdown-Quality.yml | ||
CreateIngressCert.yml | ||
IaC-bicep-AKS.yml | ||
IaC-bicep-AKSClusterOnly.yml | ||
IaC-terraform-AKS.yml | ||
README.md | ||
Shared-Services-HelmDeployNginx.yaml |
README.md
Workflows
This folder contains all the GitHub action workflows used to deploy the different components of the AKS solution. The naming convention for the workflow yaml files is as follow: [IaC|shared-servies|app]-[purpose].yml. For example a GitHub workflow intended to provision all the Azure resources for AKS using bicep will be called "IaC-bicep-aks.yml".
Reusable Workflows
All of the samples provided in this repo are written for GitHub. Many can easily be adapted for other systems by extracting the script logic used.
GitHub has a concept of Reusable Workflows, which as the name suggests promotes effective reuse of the workflow logic. Some of the samples in this repo are authored as Reusable Workflows to accelerate using them in your Action Workflow.
IaC Workflow Scenarios
The following sample workflows are provided for IaC deployments:
- IaC-bicep-AKS.yml for the deployment of AKS and all the Azure infrastructure resources that AKS depends on using bicep CARML modules.
- IaC-terraform-AKS.yml for the deployment of AKS and all the Azure infrastructure resources that AKS depends on using CAF terraform modules.
For more information, see IaC README.
Shared-Services Workflow Scenarios
- Shared-Services-HelmDeployNginx.yaml used to demonstrate the deployment of shared services through GitHub Actions. In this case NGINX is deployed. Note that there is also an option to deploy the ingress controller Traefik using GitOps (see Shared Services
Workloads Workflow Scenarios
Multiple sample workflows are provided to demonstrate different patterns for deploying applications. For more information, see Workload README.