Add install azure

getting-started/README.md

@@ -11,6 +11,7 @@ _**Getting started with Activiti Cloud**_ : here are 3 options.
 * [Using Helm](getting-started-activiti-cloud/)
   * on AWS EKS
   * on GCP GKE
+  * on Azure AKS
 
 [_**Getting started with Activiti Core**_](getting-started-activiti-core.md)_**:**_ to learn how to use the new Java Runtime API inside a Spring Boot application. This spring boot approach is using Activiti Core as a library inside your java application.
 

getting-started/getting-started-activiti-cloud/README.md

@@ -67,6 +67,8 @@ In the next section, we show you how to create a Kubernetes cluster using Amazon
 
 ### [Option B: Using Google Cloud - GKE](google-cloud-gke.md)
 
+### [Option C: Using Azure AKS](azure-aks.md)
+
 ## Step 3: Deploy Activiti Cloud Full Example
 
 The first step is to register the Activiti Cloud HELM charts into HELM running the following commands:
@@ -97,6 +99,10 @@ Use "**your-public-domain**" to deploy Activiti Helm chart in the next section.
 
 With GCP, use "**<EXTERNAL-IP>.nip.io**" to deploy Activiti Helm chart. In our case: **35.194.42.164.nip.io**
 
+### 1-c\) Configure your deployment for **Azure**
+
+With Azure, use "**<EXTERNAL-IP>.nip.io**" to deploy Activiti Helm chart. In our case: **52.237.70.174.nip.io**
+
 ### 2\) Deploy the Helm chart
 
 Once you have resolved you domain name, install Helm chart by running the Helm install command using your public domain name to set the `global.gateway.domain` key. In our case replace the string “**REPLACEME**” with the domain from previous step.
@@ -117,6 +123,12 @@ In our case for GCP, we use:
 global.gateway.domain=35.194.42.164.nip.io
 ```
 
+In our case for Azure, we use:
+
+```bash
+global.gateway.domain=52.237.70.174.nip.io
+```
+
 Here is the example result for AWS:
 
 ```text

getting-started/getting-started-activiti-cloud/azure-aks.md

@@ -0,0 +1,83 @@
+# Azure AKS
+
+## Step 1: Create a Kubernetes cluster
+
+
+### **1) Kubernetes cluster**
+
+Go to your azure portal and select the option Kubernetes Service
+{% file src="../../.gitbook/assets/azure-aks-create.png" caption="Azure portal" %}
+
+Select or create a new subscription, resource group, region and kubernetes version.
+Enter the name of cluster and DNS prefix.
+
+{% file src="../../.gitbook/assets/azure-aks-config.png" caption="Kubernetes cluster" %}
+
+Click the "Review + create"
+
+{% hint style="info" %}
+_Note: the defaults option have not been changed.
+{% endhint %}
+
+### **2) Install Azure CLI**
+
+To install the azure cli, check the site:
+https://docs.microsoft.com/pt-br/cli/azure/install-azure-cli?view=azure-cli-latest
+
+Log in and follow the installation until the end. (Next > next and next)
+
+{% hint style="info" %}
+_Note: At the end, configure your Environment Variables:
+_1. Run "set PATH=%PATH%;C:\Users\Username\.azure-kubectl" or "$env:path += 'C:\Users\Username\.azure-kubectl'" for PowerShell. This is good for the current command session.
+OR
+_2. Update system PATH environment variable by following "Control Panel->System->Advanced->Environment Variables", and re-open the command window. You only need to do it once
+{% endhint %}
+
+Once installed, check your Azure CLI version with the following command:
+
+```bash
+az --version
+```
+
+Get your credentials:
+
+```bash
+az aks get-credentials --resource-group myResourceGroup --name myAKSCluster
+```
+
+Open the page of kubernetes:
+```bash
+az aks browse --resource-group myResourceGroup --name myAKSCluster
+```
+## **Step 2: Configure HELM and install NGINX Ingress**
+
+Let's now configure HELM to work in the Cluster. We first need to give HELM permissions to deploy things into the cluster. Download the file below:
+
+{% file src="../../.gitbook/assets/helm-service-account-role.yaml" caption="helm-service-account-role.yaml" %}
+
+Run the following commands in your terminal:
+
+```bash
+kubectl apply -f helm-service-account-role.yaml
+```
+
+```bash
+helm init --service-account helm --upgrade
+```
+
+In order to be able to expose our services to be accessed from outside the cluster, we need to set up an Ingress Controller, which will automatically create routes to the internal services that we want to expose. To install the NGINX Ingress controller, run the following command:
+
+```bash
+helm install stable/nginx-ingress --version 1.1.2
+```
+
+Now that NGINX Ingress Controller is being deployed, we need to wait for it to expose itself using a Public IP. We need this Public IP to interact with our services from outside the cluster. You can find this IP by running the following command:
+
+```bash
+kubectl get svc
+```
+Example output with Azure deployment:
+
+![External IP for NGINX Ingress controller.](../../.gitbook/assets/kubectl-get-services-external-ip-azure.png)
+
+## [Step 3: Deploy Activiti Cloud Full Example](./#step-3-deploy-activiti-cloud-full-example)