You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When deploying an hybrid aks cluster via the portal the wizard creates a node pool name based on the clustername which is my case was partly uppercase. But I also wanted to deploy a additional node pool so I tried changing the name to linuxnodepool1. Partly uppercase from beginning (first screenshot) no error. But got the error (see second screenshot) when i changed the name. Al lower case no issue's (third screenshot). Only first character lower case and rest upper also works (4th screenshot).
To Reproduce
Steps to reproduce the behavior:
Create a hybrid AKS cluster from the Azure portal.
Provide necessary details and info and go to the node pools option.
See screenshots for more info
Expected behavior
When case sensitivity matters make sure it is consistent and uppercase is not allowed at all. Or leave it as is and let the code in the background handle the changing of characters to all lower case. This is odd behavior.
Screenshots
Environment (please complete the following information):
Describe the bug
When deploying an hybrid aks cluster via the portal the wizard creates a node pool name based on the clustername which is my case was partly uppercase. But I also wanted to deploy a additional node pool so I tried changing the name to linuxnodepool1. Partly uppercase from beginning (first screenshot) no error. But got the error (see second screenshot) when i changed the name. Al lower case no issue's (third screenshot). Only first character lower case and rest upper also works (4th screenshot).
To Reproduce
Steps to reproduce the behavior:
Expected behavior
When case sensitivity matters make sure it is consistent and uppercase is not allowed at all. Or leave it as is and let the code in the background handle the changing of characters to all lower case. This is odd behavior.
Screenshots
Environment (please complete the following information):
"azure-cli-core": "2.46.0",
"azure-cli-telemetry": "1.0.8",
"extensions": {
"arcappliance": "0.2.30",
"azurestackhci": "0.2.6",
"customlocation": "0.1.3",
"hybridaks": "0.2.1",
"k8s-extension": "1.4.0"
}
The text was updated successfully, but these errors were encountered: