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
As far as I can see, there's currently no way to set the maximum number of pods allowed on one node in a node pool if the Azure CNI network provider is used.
ISSUE TYPE
Feature Idea
COMPONENT NAME
azure_rm_aks
ADDITIONAL INFORMATION
This feature would basically just allow to specify how many pods can deployed on a single node in a node pool. This is already possible with other tools like the az CLI via the --max-pods parameter.
- name: Create a managed Azure Container Services (AKS) instanceazure_rm_aks:
name: myAKSlocation: eastusresource_group: myResourceGroupdns_prefix: akstestkubernetes_version: 1.14.6linux_profile:
admin_username: azureuserssh_key: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAA...network_profile:
load_balancer_sku: standardnetwork_plugin: azurenetwork_policy: azureservice_principal:
client_id: "cf72ca99-f6b9-4004-b0e0-bee10c521948"client_secret: "Password123!"agent_pool_profiles:
- name: defaultcount: 5vm_size: Standard_D2_v2max_pods: 128# <-- this is the new configuration featuretags:
Environment: Production
The text was updated successfully, but these errors were encountered:
SUMMARY
As far as I can see, there's currently no way to set the maximum number of pods allowed on one node in a node pool if the Azure CNI network provider is used.
ISSUE TYPE
COMPONENT NAME
azure_rm_aks
ADDITIONAL INFORMATION
This feature would basically just allow to specify how many pods can deployed on a single node in a node pool. This is already possible with other tools like the
az
CLI via the--max-pods
parameter.The text was updated successfully, but these errors were encountered: