Closed Sathana109 closed 4 years ago
@Sathana109 it looks like the default Kubernetes version being used is outdated, as seen here. We will update this version in the upcoming release.
In the meanwhile, you can use the -KubernetesVersion
parameter to specify the version that you use. We found that using version 1.13.5 (the latest currently supported) will successfully run this cmdlet.
@Sathana109 it looks like the default Kubernetes version being used is outdated, as seen here. We will update this version in the upcoming release. In the meanwhile, you can use the -KubernetesVersion parameter to specify the version that you use. We found that using version 1.13.5 (the latest currently supported) will successfully run this cmdlet.
I was able to create an AKS cluster successfully after using the -KubernetesVersion parameter. Thank you for the update.
Kindly let me know how to provide the values for the service principal (ClientIDandSecret) parameter. If you can provide me an example for passing values for this parameter it will be helpful.
@cormacpayne How has this cmdlet passed the basic test when it fails with the default value?
@alexandair Hey Aleksandar, the tests that run on CI don't make any live calls to Azure (for the sake of time 😁), so when a service teams introduces a test, they will run it live against Azure, capturing all of the HTTP requests and responses, which get saved to a .json
file. When the test is run on CI, we use its corresponding recorded .json
file to mock the requests and responses, which allows us to test the logic of the cmdlets, but not the Azure service itself. So when this New-AzAks
cmdlet was originally introduced, the test was recorded using a supported Kubernetes version, which still works in playback mode on CI, but would fail if ran live.
We do have tests that we run live against Azure during our releases every two weeks, but it's not an exhaustive list of calls. As we move towards generated cmdlets, we plan on generating the tests and introducing nightly live validation in some fashion, which would immediately catch these types of service-side errors.
@cormacpayne I really hope future tests will be better. If a command like New-AzAks -ResourceGroupName AKS -Name aks1
, which is the most basic usage of the New-AzAks, fails, a test is really broken. I thank you for a detailed explanation, but bugs like this look very bad in the users' eyes.
@cormacpayne , I would like to know how to pass our own service principal while creating this cluster: (ClientIDandSecret) parameter. Can you provide some examples for this?
Hi Team, can someone assist me on how to pass the ClientId and secret parameters while creating the AKS cluster?
Hi Team, Can we get any update on this?
You can't, I ended up deploying AKS using REST calls - this is the only way to fully configure it from PowerShell. Please contact me via mail if you would like the code.
cc @Azure/aks-pm
Close the issue as the issue could not be reproduced in latest version Az.Aks 1.1.2, please open new issue if the issue remains.
Description
I tried creating an AKS cluster using the command mentioned in the following document and I am facing errors: https://docs.microsoft.com/en-us/powershell/module/az.aks/New-AzAks?view=azps-2.4.0
I tried various names for the AKS cluster and still face the same error. The link given in the error message is given below: https://docs.microsoft.com/en-us/azure/aks/troubleshooting#what-naming-restrictions-are-enforced-for-aks-resources-and-parameters
Steps to reproduce
I executed the following commands:
Environment data
Module versions
Debug output
Error output