ansible

Let’s see how Azure ARM, Terraform, Azure Service Operator for Kubernetes and other solutions compare to each other so you can choose the right weapon to win the Infrastructure as Code War!

In this workshop you’ll learn how to deploy, monitor, scale, secure and debug workloads in AKS: Deploy an aplication. Configure monitoring and health checks for your application. Scale your application to meet demand. Enable SSL/TLS with an ingress controller. Secret Management with AKS & Keyvault. Debugging your Kubernetes application.

Last year I was working on a project for deploying Azure services using Ansible, and let me tell you something: Back then a feature like Visual Studio Remote Containers would have helped us so much! Why? Because just installing Visual Studio Code, the Remote Development Extension Pack, and Docker you have a killer combo that makes it possible to create a Development environment in a snap and share it with your source code.

Last May I wrote: Accepting Azure Marketplace Terms with Azure CLI and this time we’ll accomplish the same task with Ansible. Turns out that Ansible 2.6 comes with a handy new module: azure_rm_resource which lets you create, update or delete any Azure resource using Azure REST API. So I decided to take it for a test drive with the “Accepting Terms” sample.

I’ve been using Ansible and the Azure CLI every single day for the last 3 months. Non stop work editing playbooks and scripts with Visual Studio Code and running them on Ubuntu (WSL) on my Windows 10 machine. Turns out that because Ansible uses python version 2.7.12 and the Azure CLI uses python 3.6.5 you can make a mess if you get “creative” trying to install the tools instead of using the recommended commands:

NOTE: The issue described in this post was fixed!!! (ansible 2.5.2 and Azure CLI 2.0.34) # Last week I tried to run this simple Ansible playbook in Azure Cloud Shell: # resource_group.yml # Create test resource group in west europe - name: Create a Resource Group hosts: localhost connection: local gather_facts: no tasks: - name: Create Resource Group azure_rm_resourcegroup: location: westeurope name: test state: present The first attempt to run the playbook with: