Enable GitOps on an AKS Cluster

Prerequisite #82 has been completed

Once a cluster has been identified as an AKS Cluster, the AZ K8s Extension (in private preview at the time of this writing) must be used to enable GitOps on it.

The az command below requires the following command line properties to be dynamically passed given the cluster’s configuration:

• -g the name of the Resource Group where the AKS cluster was created
• -c the name of the AKS Cluster as defined in Azure. This name is usually the name of the context in the kubectl configuration, also shown for cluster name under Clusters
• --subscription the name or ID of the Azure subscription that owns the resource group.

The rest of the options shown in the sample below can remain unchanged:

az k8s-extension-private create -g [name of resource group] -c [name of cluster] -t managedClusters --name gitops --extension-type microsoft.flux --scope cluster --release-train stable --subscription [name or ID of subscription]

Due to the complexity and reliability of the potential mechanisms to discover the three variable properties that the command requires, the user should be asked to enter the three values using an applicable UI element, the name of the cluster (the value of -c) can be prefilled using the name of the cluster as shown in the Clusters tree, but the user may need to change it as this value can be edited locally.

Note that the user should be asked for these details only once, and the attributes Resource Group and Azure Cluster Name should be stored so they can be used going forward whenever actions that require the az CLI are performed against the cluster. Automatically fill in these values if they have been already provided by the user.

Note: The name of the command shown above may change once the feature goes into general availability.

[murillodigital]

@usernamehw I think this is just right! (cc. @josefaworks )

[usernamehw]

hmmm

Operation returned an invalid status ‘OK’