What happened:
Added secondary node pools due to the inflexibilities of the original nodepool.

What you expected to happen:
Expect non-default Nodepools to have kubelet stats to allow for container stat monitoring.

How to reproduce it (as minimally and precisely as possible):

Add new nodepool on existing AKS cluster, setup prometheus to scrape kubelet http-metrics from each node. Observe only the default nodepool is reachable via http://<node_IP>:10255/metrics

Anything else we need to know?:

We currently use kublet to provide container level metrics from prometheus such as CPU/memory stats among other things.

Support Ticket: 120050624005838

Environment:

• Kubernetes version (use kubectl version):

v1.16.7

• Size of cluster (how many worker nodes are in the cluster?)

This is happening on our smaller dev AKS clusters, stage and production currently. So anywhere from 1-15 nodes that vary in VM size.

• General description of workloads in the cluster (e.g. HTTP microservices, Java app, Ruby on Rails, machine learning, etc.)

Webservices/Java JVM applications

• Others:
  This is a huge pain point for us as we can't troubleshoot any container resources in our new primary nodepools.