Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updates First pass #86

Merged
merged 3 commits into from
Sep 27, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ Finally, this implementation uses a small, custom application as an example work

#### Azure platform

* AKS v1.26
* AKS v1.27
* System and User [node pool separation](https://learn.microsoft.com/azure/aks/use-system-pools)
* [AKS-managed Azure AD](https://learn.microsoft.com/azure/aks/managed-aad)
* Managed Identities for kubelet and control plane
Expand Down
2 changes: 1 addition & 1 deletion cluster-stamp.bicep
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ param gitOpsBootstrappingRepoBranch string = 'main'

/*** VARIABLES ***/

var kubernetesVersion = '1.26.0'
var kubernetesVersion = '1.27.3'

var subRgUniqueString = uniqueString('aks', subscription().subscriptionId, resourceGroup().id)
var clusterName = 'aks-${subRgUniqueString}'
Expand Down
14 changes: 2 additions & 12 deletions docs/deploy/01-prerequisites.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,25 +23,15 @@ Throughout this walkthrough, take note of the following symbol.

The Azure AD tenant backing your Cluster's API RBAC does NOT need to be the same tenant associated with your Azure subscription. Your organization may have dedicated Azure AD tenants used specifically as a separation between Azure resource management, and Kubernetes control plane access. Ensure you're following your organization's practices when it comes to separation of identity stores to ensure limited "blast radius" on any compromised accounts.

1. Latest [Azure CLI installed](https://learn.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest) (must be at least 2.37), or you can perform this from Azure Cloud Shell by clicking below.
1. Latest [Azure CLI installed](https://learn.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest) (must be at least 2.52), or you can perform this from Azure Cloud Shell by clicking below.

[![Launch Azure Cloud Shell](https://learn.microsoft.com/azure/includes/media/cloud-shell-try-it/hdi-launch-cloud-shell.png)](https://shell.azure.com/bash)

Ensure you're logged into the subscription in which you plan on deploying this reference to.

1. While the following feature(s) are still in _preview_, please enable them in your target subscription.

1. [Register the Workload Identity preview feature = `EnableWorkloadIdentityPreview`](https://learn.microsoft.com/azure/aks/workload-identity-deploy-cluster#register-the-enableworkloadidentitypreview-feature-flag)

```bash
az feature register --namespace "Microsoft.ContainerService" -n "EnableWorkloadIdentityPreview"

# Keep running until all say "Registered." (This may take up to 20 minutes.)
az feature list -o table --query "[?name=='Microsoft.ContainerService/EnableWorkloadIdentityPreview'].{Name:name,State:properties.state}"

# When all say "Registered" then re-register the AKS and related resource providers
az provider register --namespace Microsoft.ContainerService
```
_None. This reference implementation currently does not use any preview features._

1. Fork this repository and clone it locally. 🛑

Expand Down