v0.2.2 - AKS Planner capabilities, Azure Pod Identity and Kubernetes Dashboard

v0.2.2 focuses on:

• #11 Add aad-pod-identity-rabc support
• #13 Adding AKS planner capabilities
• #15 Add Kubernetes Dashboard to the feature list
  Planning an AKS cluster is an essential task, as some decisions made during the cluster creation can only be amended destroying the cluster and creating it again.

To this end, the AKS sub-generator adds the following new questions:

• Sizing assistant - What is the purpose of your cluster?
• Sizing assistant - Cluster accessibility?
• Kubernetes - Maximum nodes (The VNET will be created to accommodate this number. This decision is final and cannot be changed without destroying the cluster)
• Kubernetes - Pods per node (This decision is final and cannot be changed without destroying the cluster)
• Network (CNI) - VNET Cidr

With this information, we apply Microsoft's main Azure CNI planning checks, creating a VNET that will suit the provided answers.

A copy of the inputs and outputs of this decision process is stored in aks-plan.json, so you can review it and even share with your Networking colleagues:

{
  "params": {
    "ip": "172.0.0.0",
    "usage": "public",
    "nodes": 4,
    "podsPerNode": 110
  },
  "vnetCidr": "172.0.0.0/22",
  "dockerBridgeCidr": "172.17.0.1/16",
  "clusterSubnet": "172.0.0.0/23",
  "serviceSubnet": "172.0.2.0/23"
}

Also, RBAC users can now deploy azure-aad-pod identity out of the box by enabling the new feature:

? Kubernetes - Cluster features 
 ◉ Network plugin
 ◉ Network policy
 ◉ Role-Based Access Control (RBAC)
❯◉ Azure Active Directory Pod Id (aad-pod-id)
 ◉ Cert-manager
 ◉ Kubernetes Dashboard
 ◯ Atarraya (Experimental - Key Vault Secret Injector for AKS)
(Move up and down to reveal more choices)

And, as displayed in the previous example, Kubernetes Dashboard is now an feature you can enable as well.