...
Build step → Azure ACR Push → Azure AKS Deploy
...
Azure ACR Push Step Configuration:
...
Once the initial Step Setup is configured with the Azure ACR Push tool, set the following values:
Jenkins Tool - Select a configured Jenkins tool from Tool Registry.
Jenkins Job - Select the Azure Docker Push job that was created in the selected Jenkins tool.
Build Step - Select the name of the preceding build step.
Azure Tool - Select the configured Azure tool from Tool Registry.
Resource - Value found in the Azure portal.
Azure Registry - Select the container registry to push the images into.
Use Existing Repository - Toggle on to view and select an existing repository in the Azure Registry to push the images into. Toggle off to create a new repository where the images will be pushed. Then enter a unique name for the new repository.
Repository Name - Select the name of the repository in the container to push to.
Select Save and proceed to setting up the next pipeline steps.
...
Azure AKS Deploy Step Configuration:
Once the user has successfully created the cluster template in tasks then successfully ran it to create the cluster in Azure, they can then use the Azure AKS Deploy pipeline step to deploy docker images to the Azure Cluster. In order to run this step successfully, there needs to be a build step and an Azure ACR Push step to be successfully configured in the pipeline.
...
Once the initial Step Setup is configured with the Azure AKS Deploy tool, set the following values:
Azure Tool - Choose the tool that was used to create the Azure cluster.
Azure Credential - Drop down values will include the selected tool’s configured applications.
Cluster Name - Drop down includes successfully run clusters created in Tasks.
Generate Dynamic Service Name - When switch is enabled, a unique service name for each pipeline run using the Dynamic Name Prefix given and the run count will be generated (for example: PrefixName -1, PrefixName-2).
Service Name - Azure Service names must also be unique hence we have the ability to generate unique service names for every run based on the run count which can be enabled via the specified toggle in the pipeline step.
Host URL - Host URL is unique to user.
Service Port - This is the location where service will be deployed.
Artifact Step - Select the corresponding Azure ACR push step.
...
After all the details have been configured the step will run as a general pipeline step and the logs can be viewed from the Summary/Activity Logs table
...