some mandatory fields are missing with azure dev ops and visual studio for mac

Some Mandatory Fields Are Missing With Azure Dev Ops And Visual Studio Code Changes To

Set namespace to (namespace) we will add a variable for it later on and set Command to apply.

Im going to be using Visual Studio 2019 with the Azure Development workload, youre also going to need the Azure CLI and kubectl for future articles in this series.

This first article will guide you through deploying a basic website to AKS using Azure DevOps pipelines.

You wont need to be overly familiar with Kubernetes to follow this however a basic understanding might help.

Create a new Resource Group for your cluster, fill in the mandatory fields and set the node size and count.

On the next page select Web Application and also enable docker support for Linux.

One thing to note is that Visual Studio has generated us a Dockerfile which will be used to run our website in a containerised form.

Visual Studio will now generate us a helm chart which will allow us to deploy our application to our Kubernetes cluster.

We are going to be overriding a lot of these values as part of our CICD pipeline which is why some are set to VALUETOBEOVERRIDDEN.

At the bottom right of Visual Studio select Add to Source Control and then Git.

Give your registry a unique name and add it to our previously created resource group (Ive also set my SKU to basic) before pressing Create.

We are going to be using the classic pipelines editor for this tutorial as its slightly easier to follow so lets press Use the classic editor at the bottom.

When prompted to select a template lets go with Docker container.

A lot of the fields can be set to the same values as the fields in the Build an image task so replicate the Azure subscription, Azure Container Registry and the Image Name.

Press the button to add a new task and select Publish Build Artifacts.

Once added select the task and change Path to publish to your charts directory and set the Artifact name field to Helm.

Some Mandatory Fields Are Missing With Azure Dev Ops And Visual Studio Code Changes To

This will instruct Azure DevOps to build and push our container whenever we push code changes to the repo.

Azure DevOps will now build our container and push it to our container registry.

Hopefully we get a nice green tick showing everything has worked.

Navigate to Releases and press New pipeline, when prompted to select a template just press Empty job.

Set the Source field to the build pipeline we previously created and press Add.

First we need to setup the Tiller environment so add the Deploy to Kubernetes task, set the Service connection type to Azure Resource Manager and select the correct subscription, resource group and Kubernetes cluster.

Some Mandatory Fields Are Missing With Azure Dev Ops And Visual Studio For Mac