-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Closed
Labels
AKSAzure PS Teamfeature-requestThis issue requires a new behavior in the product in order be resolved.This issue requires a new behavior in the product in order be resolved.
Description
Description
When I issue a call to az aks list I get a large JSON document back with what appears to be a complete dump of the details related to the AKS cluster matching the input parameters.
When I make the same call to Get-AzAks I get a significantly abbreviated version of the details for the same cluster.
In particular data fields like the following appear to be missing from the output:
- aadProfile
- addonProfiles
- rbac related info
- identityProfile <--- when using
managed identity clustersthis is needed to find theUser Managed Idthat AKS/Azure creates for us. - nodeResourceGroup
....etc....etc
My expectation is that I should be able to get the exact same level of detail from Get-AzAks as I do from az aks list. For reasons beyond the scope of this bug report - I need to use the PowerShell CLI to interact with Azure instead of the Console CLI and these limitations are a significant impediment to working with AKS via PowerShell.
Steps to reproduce
Get-AzAks -ResourceGroupName {ResourceGroupContainingAksGoesHere}az aks list --resource-group {ResourceGroupContainingAksGoesHere}Environment data
$PSVersionTable
Name Value
---- -----
PSVersion 7.0.0
PSEdition Core
GitCommitId 7.0.0
OS Microsoft Windows 10.0.18363
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Module versions
Script 3.6.1 Az
Script 1.0.3 Az.AksDebug output
Error output
Metadata
Metadata
Assignees
Labels
AKSAzure PS Teamfeature-requestThis issue requires a new behavior in the product in order be resolved.This issue requires a new behavior in the product in order be resolved.