Azure Kubernetes Service (AKS)

Have feedback for Azure Kubernetes Service (AKS)? Submit your idea or vote up an idea submitted by others. All of the feedback you share here will be monitored and reviewed by the AKS team. Remember that this site is only for feature suggestions and ideas. If you have technical questions or issues, please submit them to our GitHub issues page or on StackOverflow.

How can we improve the Azure Kubernetes Service (AKS)?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Support multiple node pool

    We are currently blocked to using a single node pool in AKS. It would be good to allow us to create new node pool (in different region) and to allow us to have a different VM size (per pool). Google and Amazon are already offering that feature.

    416 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    started  ·  31 comments  ·  Support for Kubernetes features  ·  Flag idea as inappropriate…  ·  Admin →
  2. 214 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  4 comments  ·  Support for Kubernetes features  ·  Flag idea as inappropriate…  ·  Admin →
  3. Native integration between AKS and Azure Key Vault

    It makes sense to have some sort of smart integration between kubernetes secrets and azure key vault.

    I.e.
    containers:
    env:
    - name: CLIENT_ID
    valueFrom:
    azureSecretKeyRef:
    name: client-details
    key: client-id

    120 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Support for Kubernetes features  ·  Flag idea as inappropriate…  ·  Admin →
  4. Support for PodSecurityPolicy

    The PodSecurityPolicy admission controller does not seem to be supported. This is a key part of securing a cluster. I see it has previously been raised as an issue, but no feature request was raised. https://github.com/Azure/AKS/issues/327

    72 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    started  ·  3 comments  ·  Support for Kubernetes features  ·  Flag idea as inappropriate…  ·  Admin →
  5. 50 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  2 comments  ·  Support for Kubernetes features  ·  Flag idea as inappropriate…  ·  Admin →
  6. Make LsV2 series available on AKS

    Make LsV2 type available on AKS.

    We are creating an k8s operator for ScyllaDB and would like to leverage this powerful hardware (specially because of the NVMes). This would be beneficial not only to our database but to any NoSQL or applications that require fast I/O.

    32 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Support for Kubernetes features  ·  Flag idea as inappropriate…  ·  Admin →
  7. Please add an option to deploy k8s cluster with cpuManagerPolicy static.

    https://kubernetes.io/docs/tasks/administer-cluster/cpu-management-policies/#static-policy

    This option allows cpu pinning to be enabled on containers so that applications that are sensitive to context switches and require strong cpu isolation can benefit from this k8s feature.

    Please check my article regarding performance differences in ScyllaDB for a better understanding of the performance impact.

    https://www.scylladb.com/2018/08/09/cost-containerization-scylla/

    31 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Support for Kubernetes features  ·  Flag idea as inappropriate…  ·  Admin →
  8. Support PodPreset alpha feature

    https://kubernetes.io/docs/tasks/inject-data-application/podpreset/

    Some of my current workloads on acs-engine utilize PodPresets to add additional configuration to dynamically created Pods (e.g. by custom controllers which I'm not able to modify submission requests myself). It would be great if AKS would support this as well.

    The two steps required on the apiserver are:

    Adding "settings.k8s.io/v1alpha1=true" in the --runtime-config
    Adding PodPreset to --enable-admission-plugins.

    This feature request was moved from https://github.com/Azure/AKS/issues/450

    29 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Support for Kubernetes features  ·  Flag idea as inappropriate…  ·  Admin →
  9. AKS external and internal load balancer SKU

    We need to be able to pick standard SKU for out internal and external load balancers.

    21 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Support for Kubernetes features  ·  Flag idea as inappropriate…  ·  Admin →
  10. IPv6 Container Support in AKS Cluster in Private Azure VNet

    Once K8s has a final release of IPv6 (https://github.com/kubernetes/features/issues/508) I would expect it can be packaged into Azure AKS with integration in CNI, but of this I am not certain.
    I wanted to put this request here formally to track a request to support IPv6 Containers inside an Azure Dual Stack VNet and Subnet.

    21 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Support for Kubernetes features  ·  Flag idea as inappropriate…  ·  Admin →
  11. allow for changing the size of the default node size post cluster creation

    The default vm size is too small and it isn't possible to resize the default node from the docs etc.

    20 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Support for Kubernetes features  ·  Flag idea as inappropriate…  ·  Admin →
  12. 19 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Support for Kubernetes features  ·  Flag idea as inappropriate…  ·  Admin →
  13. Add support for Kubernetes Federation

    Kubernetes Federation with support for Azure DNS and traffic manager. (similar to google and amazon support of k8i Federation)

    17 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Support for Kubernetes features  ·  Flag idea as inappropriate…  ·  Admin →

    Kubernetes federation is not mature at this point. The v1 solution remains in an alpha state, with no path to GA. There is discussion around a V2 approach in sig-multicluster but it is still nascent. As a result, we have no near-term plans to enable it in AKS. If your goal is simply to run the same app across multiple clusters with traffic routing between them, you can mostly accomplish that with a good CI/CD pipeline and Azure Traffic Manager.

  14. 9 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Support for Kubernetes features  ·  Flag idea as inappropriate…  ·  Admin →
  15. Enable apiserver metrics

    Enable apiserver metrics to monitor on prometheus

    9 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Support for Kubernetes features  ·  Flag idea as inappropriate…  ·  Admin →
  16. Enable AKS node memory swapping

    I know, for most k8s setups swap is not required and should not be. Working with pod resource requests/limits is the recommended way and the slogan is "the other nodes RAM is the new swap". Container applications should have control over memory allocation.

    Still, there are circumstances where swapping really could be a benefit, as in https://github.com/kubernetes/kubeadm/issues/610#issuecomment-368856831. Another example is to handle short burst of memory allocation without crashing the pod. Rescheduling on other node may result in the same result and you need to setup a complete new cluster with larger nodes => expensive and cumbersome.

    Requesting control-plane…

    7 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Support for Kubernetes features  ·  Flag idea as inappropriate…  ·  Admin →
  17. SLA for API Service

    A formal SLA for the AKS API that's not simply based on the worker nodes (VM SLA). The reason behind this is that in some cases the component of the service that is the slowest or can become unresponsive is the API, not the deployed nodes, at least during preview testing. Also, if the API is not accessible for an extended period of time, the inability to deploy or update services on the cluster could impact business.

    7 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Support for Kubernetes features  ·  Flag idea as inappropriate…  ·  Admin →
  18. Consider adding ability to use custom CA cert

    We would like to provide the cluster with a specific CA cert to use instead of generating a new one when it's created. We have services outside AKS that needs to trust this CA and the cluster may be rebuilt and we would want to use the same CA when rebuilding it.

    6 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Support for Kubernetes features  ·  Flag idea as inappropriate…  ·  Admin →
  19. 5 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  0 comments  ·  Support for Kubernetes features  ·  Flag idea as inappropriate…  ·  Admin →
  20. Let kubernetes be aware of data disk attachment limitations or make the limit "soft"

    Currently there is a performance restraint on the data disks tied to a VM based on its size. https://blogs.technet.microsoft.com/uspartner_ts2team/2015/08/26/azure-vm-drive-attachment-limits/

    It will be good to either transform this limit to a "soft", one raising alerts instead of blocking the attachment and/or let kubernetes know that this node cannot attach new disks in order to schedule pods to different nodes.

    5 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Support for Kubernetes features  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base