Skip to content

Latest commit

 

History

History
43 lines (32 loc) · 3.08 KB

AdvancedUsage.md

File metadata and controls

43 lines (32 loc) · 3.08 KB
Raw

Advanced Usage

The QuickStart provides a nice easy way of using the Azure CLI to create your AKS Environment. However once you've done this, and are more familiar with the tool, then you'll want to initiate AKS Construction is a slightly more mature way.

Level One - Download Bicep + Your own Bicep file

  1. Use the Helper to guide your AKS configuration.
  2. Capture the parameters on the Parameters File tab to a file - this is your configuration
  3. Grab the latest release of the bicep code
  4. Author an Application Main bicep to represent your application (see here for an example)
  5. In your CI/CD system, either using one of the GitHub Action Workflow files as a base, or by coding it yourself - initiate a deployment of the bicep code, using your parameter file
  6. In your CI/CD system, deploy your application(s) to the AKS cluster

Level Two - Git symbolic link + Your own Bicep file

  1. Use the Helper to guide your AKS configuration.
  2. Capture the parameters on the Parameters File tab to a file - this is your configuration
  3. Create a Git symbolic link to the AKSC repository with this command git submodule add https://github.com/Azure/AKS-Construction.git aks-construction
  4. Author an Application Main bicep to represent your application, targetting the new aks-construction directory in your repo (see here for an example)
  5. In your CI/CD system, either using one of the GitHub Action Workflow files as a base, or by coding it yourself - initiate a deployment of the bicep code, using your parameter file
  6. In your CI/CD system, deploy your application(s) to the AKS cluster

Samples

These repo's all connect to AKS-Construction using a GIT submodule.

Sample Repo Description
aksc petclinic The Java Spring sample app, using AKS Construction bicep driven helm chart installation
selenium grid aks keda An implementation of Selenium Grid on AKS
aks workload identity Showcasing the different application identity options for accessing Azure Key Vault from AKS.

Level Three - GitHub Action Workflow

  1. Use the Helper to guide your AKS configuration.
  2. On the Deploy tab, navigate to the GitHub Actions tab
  3. Paste your Workload/Infra GitHub Repo URL into the textbox
  4. Inspect and run the script in the first script box to create an Identity in Azure and the secrets in your GitHub repo
  5. In your repo, create a new file in your .github/workflows folder, pasting in the yaml from the GitHub Actions script box
  6. Commit the file to your main branch
  7. In your repo, navigate to the actions tab and initiate the new workflow
  8. Inspect the created resources in your Azure Subscription