Skip to content

Latest commit

 

History

History
32 lines (19 loc) · 3.69 KB

referencearchs.md

File metadata and controls

32 lines (19 loc) · 3.69 KB
Raw

Referenced Projects

Enterprise Scale (Azure Landing Zones)

Enterprise Scale provides prescriptive guidance based on authoritative design for the Azure platform as a whole.

The AKS Construction helper has an Enterprise-Scale lens, with preset configurations for each landing zone area.

AKS Landing Zone Accelerator

This is the parent project that our work belongs to. The reference implementations in this repository are all focussed on guiding the creation of Landing Zones for AKS within an Enterprise Scale framework. They typically include deployments of Hub/Spoke infrastructure and development vm's, and includes a Terraform implementation.

The AKS Baseline

The AKS Construction bicep code is based on the architecture of the AKS Baseline.

The AKS Baseline is a reference architecture and has a number of additional, related reference architectures that build on the base to show different patterns such as multi-region or PCI-DSS 3.2.1 compliance.

For each of the documented architectures there is an accompanying reference implementation that includes deployment instructions and ARM templates for the cluster infrastructure. The templates showcases an end to end deployment of all the infrastructure as well as a sample workload. The ARM templates by design take a minimal amount of parameters, with much configuration built in to the resources directly. This is great from a learning perspective, and as part of making the template your own.

Much of the code and configuration in this project is based off the work in the AKS Baseline, the philosophy however is different. This project aims to converge on a single IaC codebase, and vary behaviour through parameters, parameters which use good defaults to minimise needing to provide too many parameter values. The AKS Baseline covers much of the documentation and practices, and this project focuses on the implementation experience and automation samples.

When the AKS Baseline is updated, changes are evaluated and rolled into this project. See here for a list of tagged PRs.

Deviations from the baseline (and why)

  1. System pool and user pool separation is made optional in interests of users seeking a cost optimised configuration.
  2. Ingress. Supports no ingress, AGIC integrated experience or post deployment ingress scripts for NGINX and Contour.
  3. Networking. Hub/Spoke networks typically already exist, and tightly bundling with Kubernetes doesn't work well here. BYO subnets are supported.
  4. AppGw Public Listener. AppGw is the WAF ingress point for inbound internet traffic, however private listeners are also valid for fully private environments.
  5. Cluster SLA. Is defaulted to off in interests of a more cost optimised default configuration, a parameter can be provided to opt in for the paid SLA.
  6. Monitoring Alerts. Parametrised metric analysis frequency, created two presets (1 as per baseline, 2 less frequent), set default to be much less frequent. Added extra monitoring alerts as per in-cluster suggestions.