azure-cli-extensions VS podinfo

NOTE: If you're really curious to know what the --enable-network-observability flag does in Azure CLI, you can read through the source code here

The portal is handy, but we won’t use it in this article. Instead, let’s install the Azure command-line interface. The most recent version at the moment of writing is 2.30.0.

Azure CLI

With a bit of research I was able to find a very simple solution for this problem, and Azure CLI was again my best friend.

To learn more about Azure CLI, check this documentation.

Azure CLI installed and connected to your subscription

4) All the next steps that we're about to do can be done with the UI in Azure Portal, but we will use Azure CLI as much as possible. Also, I will name my Resource Group and App Service Plan as MyResourceGroup and MyLinuxPlan respectively. If you already have a Resource Group and App Service plan, you can continue using them. Or you can follow next step and substitute with names of your own choosing.

Bicep comes with a CLI that you can install locally on Windows, MacOS, and Linux. That gives you the ability to build and deploy your Bicep files with Azure CLI.

Azure CLI

I would recommend setting up a simple Kubernetes cluster (maybe using KinD, minikube, or something similar) and getting to know how it works (you could try deploying something like Kuard or Podinfo or deploy one of your own containerized apps to Kubernetes).

Podinfo does something very similar while coming with alot of additional features.

A more mature example: https://github.com/stefanprodan/podinfo, k8s specific.

Try this podinfo implementation.

I have chosen the well known podinfo application as an example, and I have developed the base and some components associated to it.

Check out https://github.com/stefanprodan/podinfo it’s my go to for creating new microservices

It focuses on an "uninteresting" workload and uses podinfo as the sample app. This is because it's easy to deploy and customize with a sample Helm chart.