When working with a tool like Azure it is very important to make a good friendship with its documentation link
to setup Azure we will need two main components

• kubectl
• minikube
• virtual box(optional)

if you have any problem or error during the setup you can refer to google.....

Step One

First we need to install kubectl through which we will manage Azure.
if you are using linux just copy and paste these commands one by one.

Step Two

Now we will install minikube, when using minikube 8Gb RAM is recommended.
if you are using linux then just copy and paste these commands one by one.

Step Three

In this step we will install virtual box which is optional, if you want to use virtual box then make sure your machine supports virtualization
To check that your system supports virtualization or not run the command below
grep -E --color 'vmx|svm' /proc/cpuinfo if this command returns some output then you are good to go else continue without install virtual box.

Step Four

Lets check that we installed all 3 or 2 main tools correctly or not.
Run the commands that is based on your criteria.
if one fails because of any error use the command below and then try next command. minikube delete

If minikube Starts

If minikube starts then you can type the below command to get its status

minikube status

this command will return result similler to
host: Running kubelet: Running apiserver: Running

Now its all set to us Azure :-)

Link to official docs
it is like a container that can contain different azure resources, we usr RG to deploy resource according to some logical context

Important notes about RGs

• If you delete a resource group all the resources in that RG will be deleted

RG using Azure cli

az group create \
    --name "<name of rg>" \
    --location "location or region>"

Link to official docs
it is a resource of Azure similer to a windows or linux computer system. It is mostly used when an application requires a custom configuration or you want full control over the environment where your application is going to be deployed.
Below is the minimum set of configuration to deploy a vm

Important notes about VMs

• vm is a resource
• deployed in a resource group
• vm size can be changed after deployment
• steps : Rg->vm->vm ports->public ip

VM using Azure cli

you can mainly make 2 types of vms

• windows vm
• Linux vm

az vm create \
    --resource-group "<name of rg>" \
    --name "<name of vm>" \
    --image "window" \
    --admin-username "<windows admin user-name>" \
    --admin-password "<windows admin password>"

az vm create \
    --resource-group "<name of rg>" \
    --name "<name of vm>" \
    --image "Linux" \
    --admin-username "<linux admin user-name>" \
    --authentication-type "ssh" \
    --ssh-key-value <path to .pub file>

After deploying a vm you may want to access it using RDP or ssh, for that you have to open the specific port on the newly created vm

az vm open-port \
    --resource-group "<name of rg>" \
    --name "<name of vm>" \
    --port "3389 or 22"

for loging in the vm you might also need the public ip of the vm for that you can use the command below

az vm list-ip-addresses \
    --resource-group "<name of rg>" \
    --name "<name of vm>" \
    -output table

Link to official docs
It isAzure resource used as a private container image repository.

Important notes about VMs

• ACR is a resource
• deployed in a resource group
• build, store & manage images
• steps : Rg->ACR->ACR login->push image or code to build image
• use headless authentication for intigrating with other applications for automation

az acr create \
      --resource-group "<name of rg>" \
      --name "<name of ACR globally unique>" \
      --sku "Basic, Standard or Premium"

az acr login --name "<name of ACR>"

az acr show \
      --name "<name of ACR>" \
      --query loginServer \
      --output table

docker tag <image id> <login server>/<image name>:<tag>

docker push <login server>/<image name>:<tag>

az acr build 
      --image "<name of future image>:"<tag>" \
      --registry "<ACR name>" \
      "<path to Dockerfile>"

az acr repository list --name "<name of ACR>" --output table

az acr repository show-tags list --name "<name of ACR>" --repository "<name of repository or image>" --output table

Link to official docs
it is a resource that lets you run docker container serverlessly(without managing base Os).Azure Container Instances is a solution for any scenario that can operate in isolated containers, without orchestration.

Important notes about ACI

• ACR is a resource
• serverless container platform
• allows access applications via internet or vNet
• supports both windows and linux containers
• configuable resource size
• can presist dataif needed using azure files
• can be deployed in group
• has restart policy
• better for event driven architecture
• steps: create container

Link to official docs
it is a resource that enables you to build and host web apps, mobile back ends, and RESTful APIs in the programming language of your choice without managing infrastructure.Code to deploy comes from git or other systems

Important notes about App Service

• App Service is a resource
• web based hosting
• supports both windows and linux apps
• security, load balencing & automation
• cost depends on App Service Plan
• steps: app service plan->create webapp

There are two types of App Service plans

• Non isolated app service plan
• Isolated app service plan

Non isolated app service plan

• Free and shared (F1, D1)
• Basic (B1, B2, B3) manual scale
• Standard (S1, S2, S3) can auto scale Recomended for production
• Premium v2(P1v2, P2v2, P3v2)
• Premium v3(P1v3, P2v3, P3v3)

Isolated app service plans (ASE)

to consider when

• fully isolated environment for web app
• highly scalable & recomended for high memory utlization apps
• isolated & secure nettwork access
• fine control ofver network traffic
• can connect using VPN

plans available :

• I (I1,I2, I3)
• Iv2 (I1v2, I2v2, I3v2)

az appservice plan create --name "%lt;plan name>" \
                            --resource-group "<name of rg>" \
                            --sku s1 \
                            --is-linux

az webapp create -g "<name of rg>" \
                            -p "<name of app service plan>" \
                            -n "<name of webapp>" \
                            --runtime "node|10.14"

Link to official docs
It is a serverless platform to run small peices of code. It can auto scale &you have to pay only for the time yur code runs (consumption plan)
one ting to note is that azure functions run on app service plan and we have the following plans :

• consumption plan (5 min limit timeout)
• app service plan (Traditional pricing)
• premium plan (high speed, secuity, reserved instance)

Important notes about Azure Functions

• Azure Functions is a resource
• run functions serverlessly
• auto scales
• cost depends on App Service Plan
• steps: RG->app service plan->functions app(func init)->func new

Duable Functions

are azure one or mores fuctions chained together mostly used for serverless workflows (orcastrations).

Orchestration patterns

• function chaining
• fan out- fan in , exectes activityfunctions in parallel and waits for them to end
• async http apis
• monitor
• human interaction

Azure functions App

is a resource used to group function in a single context

Development & workflow

you can write all the code manually but that is not a good choice, so we have mainly 2 ways to develop locally and then dpeoy.

• Visual studio
• Visual studio code with Azure core tools

Working with Azure Core Tools

Azure core tools is a cli application that helps to develop Azure functions locally and deploy to cloud by providing templates & easy commands for automation.

Create function project locally

• create functions project

  func init <projectName>

• create new function

  func new

• start functions to test locally

  func start

• deploy or publish to azure

  func azure functionapp publish <FunctionAppName>

Link to official docs
It is a Fast NoSQL database with open APIs for any scale.

Important notes about Azure Csmos DB

• Azure Cosmos DB is a resource
• provides low latency < 10ms
• elastic scalabilty
• pricing for throughput
• builtin indexing
• steps: RG->cmos db account->database->container(Table, Graph or collection)-> items

APIs that Cosmos DB provides

Cosmos db provides with a wide rage of apis to intract with the database.You can chose which API on the basics of with which you are familier or some other tradeoffs.
Here are the APIs

• SQL default
• Cassandra
• Mongo db
• Gremlin
• Azure Table

Lets have a look on each and see, Why you should you prefer a specific over other APIs.

SQL

• if you know SQL
• you want to store data as json documents
• if know other case fits choose SQL

Cassandra

• if you know CQL
• easy to migrate cassandra based dbs to cloud.
• want to store data in wide coloumn format

Mongo db

• if you know mongodb
• easy to migrate mogodbs to cloud.
• want to use json document store

Gremlin

• need to store graph relations between data

Azure Table storage

• if you know azure table storage
• part of azure storage
• easy to migrate azure table storage to Cosmos db.

Selecting SDK

• If using SQL API then use latest cosmosdb SDK for your platform
• If using cassandra, mongodb or gremin use current sdk
• If using Azure table api use current table sdks

Consistancy Levels

• Strong : gurantees that reads get the most recent version of an item
• bounded staleness : gurantees that reads has a max lag of (either version or time)
• session consistency : gurantees that clients sessio will reads its own writes.
• consistent prefix consistancy : gurantees that updates are returned in order.
• Eventual Consistancy : provides no gurantee for order.

Link to official docs
Azure Blob Storage is Microsoft's object storage solution for the cloud. Blob storage is optimized for storing massive amounts of unstructured data.

Important notes about Azure Blob Storage

• It is an object storage for the cloud
• You can store unstructured data like text files(html, json, logs) binary files(images, videos, pdfs, virtial disks of vm)
• accessabe via REST API over HTTP/HTTPS
• steps : RG->create storage account(globally unique name)-> create Blob containers->blobs(files)

Authorize access to blob storage

azure blob storage provides many ways to provide authorized access to objects, along with the different access levels

Access levels

• private (no read access without authorization)
• Blob (can't list blobs in container)
• Container (can list blobs in the container)

Authorization Types

• shared key (storage account key)
• shared access signature (SAS token)
• Azure active directory
• Anonymous (public read access)

Blob Types

• block blob (images , videos)
• append blob (log files)
• page blobs (virtual disks)

Replication and Redundancy

• LRS : create 3 copies in the same zone (data center).
• ZRS(not supported in all regions) : creates 3 copies in 3 different zones(data centers) in the same region.
• GRS : creates 3 copies in the same zone (data center) & 3 copies in a zone(data center) of secondary region.
• GZRS : creates 3 in 3 different zones(data centers) in primaery region & 3 copies in a zone(data center) of secondary region.
• RA-GRS (default for Storage v2): same as GRS but you can read from secondary region.
• RA-GZRS : same as GZRS but you can read from secondary region.

actually it is not a resource of Azure it is mostly written or defined in the spec: of Pods.
it actually helps us to share data between containers or whole cluster, not only that but also allow us to retain data if the pod or the container is deleted. you can say that it store & share data on the pod level
there are many types of volumes.

• empty dir
• configmam, secret, downward API
• presistant vloumes
• git repo
• gce presistant disk
• aws Elastic block storage
• Azure disk

presistant volumes are a little different than other volumes as the store & share data on the cluster level
it also works a little differently. Below are the steps to use and work with persistent volume (pv).

1. Make a persistent volume (pv)
2. Make a persistent volume claim (pvc)
3. Mount it in a pod as volume using (pvc)

In this section we will see tools for configuration and deployments provided by Azure.

It is a resource of kuberenetes that helps us to deploy update application very easily by providing some strategies.
basically it makes a replica-set and manages that. it does not interact with any pod directly. link to documentation

Properties of Azure resources that can be added to any resource.