New AKS Deploy #22
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # This workflow will build and push an application to a Azure Kubernetes Service (AKS) cluster when you push your code | |
| # | |
| # This workflow assumes you have already created the target AKS cluster and have created an Azure Container Registry (ACR) | |
| # The ACR should be attached to the AKS cluster | |
| # For instructions see: | |
| # - https://docs.microsoft.com/en-us/azure/aks/kubernetes-walkthrough-portal | |
| # - https://docs.microsoft.com/en-us/azure/container-registry/container-registry-get-started-portal | |
| # - https://learn.microsoft.com/en-us/azure/aks/cluster-container-registry-integration?tabs=azure-cli#configure-acr-integration-for-existing-aks-clusters | |
| # - https://github.com/Azure/aks-create-action | |
| # | |
| # To configure this workflow: | |
| # | |
| # 1. Set the following secrets in your repository (instructions for getting these can be found at https://docs.microsoft.com/en-us/azure/developer/github/connect-from-azure?tabs=azure-cli%2Clinux): | |
| # - AZURE_CLIENT_ID | |
| # - AZURE_TENANT_ID | |
| # - AZURE_SUBSCRIPTION_ID | |
| # | |
| # 2. Set the following environment variables (or replace the values below): | |
| # - AZURE_CONTAINER_REGISTRY (name of your container registry / ACR) | |
| # - RESOURCE_GROUP (where your cluster is deployed) | |
| # - CLUSTER_NAME (name of your AKS cluster) | |
| # - CONTAINER_NAME (name of the container image you would like to push up to your ACR) | |
| # - IMAGE_PULL_SECRET_NAME (name of the ImagePullSecret that will be created to pull your ACR image) | |
| # - DEPLOYMENT_MANIFEST_PATH (path to the manifest yaml for your deployment) | |
| # | |
| # For more information on GitHub Actions for Azure, refer to https://github.com/Azure/Actions | |
| # For more samples to get started with GitHub Action workflows to deploy to Azure, refer to https://github.com/Azure/actions-workflow-samples | |
| # For more options with the actions used below please refer to https://github.com/Azure/login | |
| name: New AKS Deploy | |
| on: | |
| workflow_dispatch: | |
| env: | |
| AZURE_CONTAINER_REGISTRY: "jaz400acr" | |
| CONTAINER_NAME: "docker-app" | |
| RESOURCE_GROUP: "az400" | |
| CLUSTER_NAME: "az400" | |
| DEPLOYMENT_MANIFEST_PATH: "deployment.yml" | |
| jobs: | |
| buildImage: | |
| name: Build and Push Image | |
| permissions: | |
| contents: read | |
| id-token: write | |
| runs-on: ubuntu-latest | |
| environment: production | |
| steps: | |
| # Checks out the repository this file is in | |
| - uses: actions/checkout@v4 | |
| # Logs in with your Azure credentials | |
| - name: Azure login | |
| uses: azure/login@v2 | |
| with: | |
| client-id: ${{ secrets.AZURE_CLIENT_ID }} | |
| tenant-id: ${{ secrets.AZURE_TENANT_ID }} | |
| subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }} | |
| enable-AzPSSession: true | |
| # Deploy ACR using Bicep | |
| - name: Deploy ACR using Bicep | |
| uses: azure/arm-deploy@v2 | |
| with: | |
| subscriptionId: ${{ secrets.AZURE_SUBSCRIPTION_ID }} | |
| resourceGroupName: ${{ env.RESOURCE_GROUP }} | |
| template: azd/acr/modules/acr.bicep | |
| parameters: "registryName=${{ env.AZURE_CONTAINER_REGISTRY }}" | |
| failOnStdErr: false # Deploy AKS using Bicep | |
| - name: Deploy AKS using Bicep | |
| uses: azure/arm-deploy@v2 | |
| with: | |
| subscriptionId: ${{ secrets.AZURE_SUBSCRIPTION_ID }} | |
| resourceGroupName: ${{ env.RESOURCE_GROUP }} | |
| template: azd/aks/modules/aks.bicep | |
| parameters: "aksClusterName=${{ env.CLUSTER_NAME }} acrResourceId=/subscriptions/${{ secrets.AZURE_SUBSCRIPTION_ID }}/resourceGroups/${{ env.RESOURCE_GROUP }}/providers/Microsoft.ContainerRegistry/registries/${{ env.AZURE_CONTAINER_REGISTRY }}" | |
| failOnStdErr: false | |
| # Ensures AKS has access to the ACR | |
| - name: Ensure AKS has access to the ACR # REcommended permission is Role Based Access Control Administrator | |
| run: | | |
| az aks update --name ${{ env.CLUSTER_NAME }} --resource-group ${{ env.RESOURCE_GROUP }} --attach-acr ${{ env.AZURE_CONTAINER_REGISTRY }} | |
| # Builds and pushes an image up to your Azure Container Registry | |
| - name: Build and push image to ACR | |
| run: | | |
| az acr build --image ${{ env.AZURE_CONTAINER_REGISTRY }}.azurecr.io/${{ env.CONTAINER_NAME }}:latest --registry ${{ env.AZURE_CONTAINER_REGISTRY }} -g ${{ env.RESOURCE_GROUP }} . | |
| deploy: | |
| name: Deploy to AKS | |
| permissions: | |
| actions: read | |
| contents: read | |
| id-token: write | |
| runs-on: ubuntu-latest | |
| environment: production | |
| needs: [buildImage] | |
| steps: | |
| # Checks out the repository this file is in | |
| - uses: actions/checkout@v4 | |
| # Logs in with your Azure credentials | |
| - name: Azure login | |
| uses: azure/login@v2 | |
| with: | |
| client-id: ${{ secrets.AZURE_CLIENT_ID }} | |
| tenant-id: ${{ secrets.AZURE_TENANT_ID }} | |
| subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }} | |
| enable-AzPSSession: true | |
| # Use kubelogin to configure your kubeconfig for Azure auth | |
| - name: Set up kubelogin for non-interactive login | |
| uses: azure/use-kubelogin@v1 | |
| with: | |
| kubelogin-version: "v0.0.25" | |
| # Retrieves your Azure Kubernetes Service cluster's kubeconfig file | |
| - name: Get K8s context | |
| uses: azure/aks-set-context@v3 | |
| with: | |
| resource-group: ${{ env.RESOURCE_GROUP }} | |
| cluster-name: ${{ env.CLUSTER_NAME }} | |
| admin: "false" | |
| use-kubelogin: "true" | |
| # Deploys application based on given manifest file | |
| - name: Deploys application | |
| uses: Azure/k8s-deploy@v4 | |
| with: | |
| action: deploy | |
| manifests: ${{ env.DEPLOYMENT_MANIFEST_PATH }} | |
| images: | | |
| ${{ env.AZURE_CONTAINER_REGISTRY }}.azurecr.io/${{ env.CONTAINER_NAME }}:latest |