PSAksDeployment

Overview

Azure Kubernetes Service (AKS) makes provisioning Kubernetes clusters very easy, in a "Hello World!" kind of way.

But deploying a production-ready Kubernetes cluster requires additonal components and considerations :

Monitoring (with metrics and logs)
Kubectl configuration
How to deploy resources (Helm and Tiller)
Routing requests from the outside world to services in the cluster (ingress controller)
Issuing and managing TLS certificates for ingress controller(s)

PSAksDeployment is a PowerShell module which facilitates all of the above by provisioning and configuring extra resources, in addition to the Azure AKS resource.

It is an opinionated implementation, in the sense that :

Log aggregation and querying is done with Azure Monitor (with Log Analytics)
The metrics collection/querying/alerting solution is Prometheus
The metrics charting/graphing/dashboard solution is Grafana
The ingress controller is NGINX Ingress Controller
Management Kubernetes resources are deployed into a "management" namespace
The solution to manage TLS certificates is cert-manager (with Let's Encrypt)
The ingress controller TLS certificate is propagated to other namespaces (including namespaces created at a later point), to allow ingresses in any namespace to use it, using a custom tool : secret-propagator

Requirements

To use PSAksDeployment, you need :

Windows PowerShell 5.1
.Net Framework 4.7.2 (required by the "Az" PowerShell modules)

All other prerequisites can be installed by running Install-PSAksPrerequisites, for example :

Install-PSAksPrerequisites -InstallationFolder 'C:\Tools'

This installs the following (if they are not already installed) :

Az PowerShell modules (PSAksDeployment is not compatible with the legacy AzureRM modules)
Terraform
Kubectl
Helm

It also adds the specified installation folder to your PATH environment variable (if not already in the PATH).

Installation

From the PowerShell Gallery

The easiest and preferred way to install PSAksDeployment is via the PowerShell Gallery.

Run the following command to install PSAksDeployment and its dependencies ("Az" PowerShell modules) :

Install-Module -Name 'PSAksDeployment' -Repository 'PSGallery'

From Github

As an alternative, you can clone this repository to a location on your system and copy the PSAksDeployment subfolder into : C:\Program Files\WindowsPowerShell\Modules\.

NOTE : In this case, you need to install the Azure PowerShell modules yourself, like so :

Install-Module -Name 'Az.Profile', 'Az.Resources', 'Az.Aks' -Repository 'PSGallery'

Getting Started

Deploying a new AKS cluster

This is the purpose of Invoke-PSAksDeployment.

It deploys the following :

an Azure Kubernetes Service (AKS) instance
an Azure Log Analytics workspace with the ContainerInsights solution
a Public IP address for the ingress controller
a "management" namespace
Tiller
NGINX Ingress Controller
cert-manager
a TLS certificate (to support HTTPS ingresses)
secret-propagator
Prometheus (HA setup for the server component)
Grafana

It primarily acts as an input validation and orchestration layer. Under the hood, most of the work is done by applying Terraform configurations.

Due to the nature of what it does, Invoke-PSAksDeployment takes a large number of parameters :

PS C:\> Import-Module -Name 'PSAksDeployment'
PS C:\> (Get-Command -Name 'Invoke-PSAksDeployment').Parameters.Keys
ServicePrincipalID
ServicePrincipalSecret
AzureTenantID
Subscription
ClusterName
ClusterLocation
LogAnalyticsWorkspaceLocation
KubernetesVersion
NodeCount
NodeSize
OSDiskSizeGB
MaxPodsPerNode
Environment
LetsEncryptEmail
TerraformOutputFolder
ConfigPath

You may be wondering :

What are these for ?
Which ones are mandatory ?
What is the default value ?
What are the possible values ?

You can get this information via the cmdlet help, for example :

PS C:\> Get-Help 'Invoke-PSAksDeployment' -Parameter 'ServicePrincipalID'

-ServicePrincipalID <String>
    The application ID of the Service Principal used by Terraform (and the AKS cluster) to access Azure.

    Required?                    true
    Position?                    1
    Default value
    Accept pipeline input?       false
    Accept wildcard characters?  false

Doing this for each parameter can be tedious, so there is another way to specify all inputs to Invoke-PSAksDeployment : a configuration file.

New-PSAksDeploymentConfig scaffolds this configuration file, with helpful information for each parameter :

a description
the data type
valid values
the default value

Here is an example :

PS C:\> $ScaffoldParams = @{
>>     ServicePrincipalID     = '29x1ecd3-190f-42c9-8660-088f69d121zn'
>>     ServicePrincipalSecret = 'tsWpRr6/YCxNyh8efMvjWbe5JoOiOw03xR1o9S5CLhZ='
>>     AzureTenantID          = '96v3b174-9c1p-4a5e-9177-18c3bccc87cb'
>>     Subscription           = 'DevOps'
>>     ClusterLocation        = 'North Europe'
>>     Path                   = '.\TestScaffold.psd1'
>> }
PS C:\> New-PSAksDeploymentConfig @ScaffoldParams

Here is what the generated file looks like :

PS C:\> Get-Content .\TestScaffold.psd1
@{
    <#
    The name of the Azure subscription where the AKS instance (and other Azure resources) will be deployed.
    Type : String
    Valid values : "DevOps", "ANY OTHER SUBSCRIPTION WHICH CAN BE ACCESSED BY THE SERVICE PRINCIPAL"
    #>
    Subscription = ""

    <#
    The Azure region where the AKS cluster (and other Azure resources) will be deployed.
    Type : String
    Valid values : "East US", "West Europe", "Central US", "Canada Central", "Canada East", "UK South", "West US", "West US 2", "Australia East", "North Europe", "Japan East", "East US 2", "Southeast Asia", "UK West", "South India", "East Asia"
    #>
    ClusterLocation = ""

    <#
    The Azure region where the Log Analytics workspace will be deployed.
    This might not be possible to provision the Log Analytics workspace in the same region as the AKS cluster, because Log Analytics is available in a limited set of regions.
    Type : String
    Valid values : "East US", "West Europe", "Southeast Asia", "Australia Southeast", "West Central US", "Japan East", "UK South", "Central India", "Canada Central"
    #>
    LogAnalyticsWorkspaceLocation = ""

    <#
    The application ID of the Service Principal used by Terraform (and the AKS cluster) to access Azure.
    Type : String
    Valid values :
    #>
    ServicePrincipalID = ""

    <#
    The password of the Service Principal used by Terraform (and the AKS cluster) to access Azure.
    Type : String
    Valid values :
    #>
    ServicePrincipalSecret = ""

    <#
    The ID of the Azure AD tenant where the Terraform Service Principal (and the target subscription) live.
    Type : String
    Valid values :
    #>
    AzureTenantID = ""

    <#
    The name of the AKS cluster.
    The name of the resource group and the cluster DNS prefix are derived from this value.
    Type : String
    Valid values : The name can contain only letters, numbers, and hyphens. The name must start with a letter and must end with a letter or a number.
    #>
    ClusterName = ""

    <#
    The version of Kubernetes software running in the AKS Cluster.
    Type : String
    Valid values : "1.9.11", "1.10.12", "1.10.13", "1.11.8", "1.11.9", "1.12.6", "1.12.7", "1.13.10"
    #>
    KubernetesVersion = "1.13.10"

    <#
    The number of worker nodes in the AKS cluster.
    Type : Int32
    Valid values : Between 1 and 100.
    #>
    NodeCount = 3
  ...

}

(Output cut for brevity)

Now, you can populate/adjust values in the file to your needs and feed it to Invoke-PSAksDeployment, like so :

PS C:\> Invoke-PSAksDeployment -ConfigPath '.\TestScaffold.psd1'

Sit back and relax, the overall deployment takes around 20-25 minutes.

When it completes, Kubernetes management tools are ready to work with your new cluster.
For example, you can list the deployments in the "management" namespace :

PS C:\> kubectl get deployment -n management
NAMESPACE     NAME                            DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
management    cert-manager                    1         1         1            1           5m
management    nginx-ingress-controller        2         2         2            2           11m
management    nginx-ingress-default-backend   1         1         1            1           11m
management    secret-propagator               1         1         1            1           3m

Or list all Helm releases :

PS C:\> helm ls
NAME                 REVISION    UPDATED                       STATUS         CHART                   APP VERSION   NAMESPACE
cert-manager         1           Sun Dec  9 18:49:40 2018      DEPLOYED       cert-manager-v0.5.2     v0.5.2        management
cluster-issuer       1           Sun Dec  9 18:49:51 2018      DEPLOYED       cluster-issuer-0.1.0    1.0           default
nginx-ingress        1           Sun Dec  9 18:43:16 2018      DEPLOYED       nginx-ingress-1.0.1     0.21.0        management
secret-propagator    1           Sun Dec  9 18:51:40 2018      DEPLOYED       secret-propagator-0.1.0 1.0           management

To open the Prometheus web interface, run the following commands :

PS C:\> $PromSvcPort = kubectl get svc prometheus-server -n management -o jsonpath="{.spec.ports[?(@.name=='http')].port}"
PS C:\> kubectl -n management port-forward svc/prometheus-server 9090:$PromSvcPort
PS C:\> start "http://localhost:9090"

To login to Grafana web interface, we first need to get the admin account password :

PS C:\> $Base64Passwd = kubectl get secret grafana -n management -o jsonpath="{.data.admin-password}"
PS C:\> [Text.Encoding]::UTF8.GetString([Convert]::FromBase64String($Base64Passwd))

To access the Grafana web interface, run the following :

PS C:\> $GrafanaSvcName = kubectl get svc -n management -l "app=grafana" -o jsonpath="{.items[0].metadata.name}"
PS C:\> $GrafanaSvcPort = kubectl get svc $GrafanaSvcName -n management -o jsonpath="{.spec.ports[0].port}"
PS C:\> kubectl -n management port-forward svc/$GrafanaSvcName 3000:$GrafanaSvcPort
PS C:\> start "http://localhost:3000"

You can now login with username admin and the password obtained in the previous step.

Deleting the AKS cluster (and all associated resources)

An AKS cluster deployed with Invoke-PSAksDeployment may need to be later deprovisioned.

In this case, the cmdlet Remove-PSAksDeployment automates tearing down the Azure Kubernetes Service instance and all associated resources, to stop incurring any Azure charges.

Here is an example usage :

PS C:\> $DestroyParams = @{
>>     ServicePrincipalID     = '29x1ecd3-190f-42c9-8660-088f69d121zn'
>>     ServicePrincipalSecret = 'tsWpRr6/YCxNyh8efMvjWbe5JoOiOw03xR1o9S5CLhZ='
>>     AzureTenantID          = '96v3b174-9c1p-4a5e-9177-18c3bccc87cb'
>>     Subscription           = 'DevOps'
>>     ClusterName            = 'docs-cluster'
>> }
PS C:\> Remove-PSAksDeployment @DestroyParams

Contributing to PSAksDeployment

You are welcome to contribute to this project. There are many ways you can contribute :

Submit a bug report.
Submit a fix for an issue.
Submit a feature request.
Submit test cases.
Tell others about the project.
Tell the developers how much you appreciate the project !

For more information on how to contribute to PSAksDeployment, please refer to the contributing guidelines document.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

README.md

README.md

PSAksDeployment

Overview

Requirements

Installation

From the PowerShell Gallery

From Github

Getting Started

Deploying a new AKS cluster

Deleting the AKS cluster (and all associated resources)

Contributing to PSAksDeployment

Files

README.md

Latest commit

History

README.md

File metadata and controls

PSAksDeployment

Overview

Requirements

Installation

From the PowerShell Gallery

From Github

Getting Started

Deploying a new AKS cluster

Deleting the AKS cluster (and all associated resources)

Contributing to PSAksDeployment