This repo might serve as a starting point to deploy an full ELK cluster in a AKS by using an HELM package.
The deployment might not be production ready and it might not contain security patches. Kindly review the template before using it in Prod.
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
As a first thing - you should have an Azure Account setup and a subscription ready to be used.
Make sure that you are selecting the correct Subscription by running the following AzCli command "az account show"
Once you have the subscription sorted out, just run the init.ps1 script. This will create an RG which it will contain the storage account used by Terraform to store the state of the plans that we will be executing.
Open init.ps1 and change the variables as you need before running it. Changing the init.ps1 might also require changes on the "backend" block of each provider.tf
After that make sure to have Helm and Kubectl installed on your PC.
An AKS cluster needs to be deployed. The terraform template provided will deploy an AKS in a private VNET and it will use an AppGateway to provide public IPs to the cluster by an Ingress.
- Open a cmd or powershell.
- cd into the AKS_Cluster folder.
- Terraform init
- Terraform apply -var="name_prefix=pick_your_prefix"
We will not use Helm to install the ELK cluster.
- Open a cmd or powershell.
- cd into the ELK folder.
- Review the values on values.yaml.
- Run helm dependency build.
- Get the AKS credentials from the AKS dashboard on the Azure portal. This will setup connection for the Kubectl.
- Run helm install [name_of_my_release] ..
To confirm that the installation was successful, run the following command:
- Open a cmd or powershell.
- kubectl get pod,svc,ingress,sts -o wide
The ingress should have a public IP assigned to it by the Application Gateway and you should be able to open it in a browser.