Azure / Azure/azure-libraries-for-java
[FEATURE REQ] Azure Container Service (AKS) define with RBACenabled true is not possible?
- Vorherrschende Sprache
- Java
- Sterne
- 97
- Forks
- 102
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
I am using the azure-libraries-for-java to create a kubernetes cluster with withRBACEnabled true. The define() does not have the option withRBACEnabled and the cluster cannot be updated to set this property.
KubernetesCluster kubernetesCluster = azure.kubernetesClusters().define(kubernetesClusterVO.getAksName())
.withRegion(kubernetesClusterVO.getRegion())
.withNewResourceGroup(kubernetesClusterVO.getResourceGroupName())
.withLatestVersion()
.withRootUsername(kubernetesClusterVO.getRootUserName())
.withSshKey(sshKeys.getSshPublicKey())
.withServicePrincipalClientId(kubernetesClusterVO.getServicePrincipalClientId())
.withServicePrincipalSecret(kubernetesClusterVO.getServicePrincipalSecret())
.defineAgentPool(kubernetesClusterVO.getAgentpoolName())
.withVirtualMachineSize(kubernetesClusterVO.getVMSizeType())
.withAgentPoolVirtualMachineCount(kubernetesClusterVO.getAgentPoolVMCount())
.attach()
.withDnsPrefix(kubernetesClusterVO.getDnsNamePrefix())
.create();
The cluster is created with RBACEnabled false. No option to change it.
Update attempt using the java library
/**…more code..**/
item = item.update()
.withRBACEnabled()
.apply();
Error description
com.microsoft.azure.CloudException: Changing property 'enableRBAC' is not allowed.: Changing property 'enableRBAC' is not allowed.
Thank you.
Beitragsleitfaden
Rechercherichtung
Start from the KubernetesCluster define() and update() entry points shown in the issue, then trace how AKS properties are sent during cluster creation. Check the Azure model and existing tests for enableRBAC support. Done means the Java library can request RBAC during creation and clearly handles the update limitation.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- azure, java, kubernetes
- Bereich
- cloud, infrastructure
- Issue-Typ
- Feature
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 35/100