After connecting ACI to AKS, pods are created on the AKS nodes and not in ACI

[jungopro]

Setup

I have an AKS cluster with 1 AKS node

I installed helm and deployed the ACI connecter using az aks install-connector --name myAKSCluster --resource-group acidemo --connector-name aci-connector

$ kubectl get nodes
NAME                                  STATUS    ROLES     AGE       VERSION
aks-nodepool1-34825167-0              Ready     agent     23m       v1.7.9
virtual-kubelet-aci-connector-linux   Ready     agent     22s       v1.8.3

Problem

When I deploy a chart I see the pods on the AKS node and not the ACI

$ helm install stable/prometheus
NAME:   xrayed-giraffe
LAST DEPLOYED: Mon Mar 26 14:15:53 2018
NAMESPACE: default
STATUS: DEPLOYED

RESOURCES:
==> v1/PersistentVolumeClaim
NAME                                    STATUS   VOLUME   CAPACITY  ACCESSMODES  STORAGECLASS  AGE
xrayed-giraffe-prometheus-alertmanager  Pending  default  3s
xrayed-giraffe-prometheus-server        Pending  default  3s

==> v1/Service
NAME                                          CLUSTER-IP    EXTERNAL-IP  PORT(S)   AGE
xrayed-giraffe-prometheus-alertmanager        10.0.116.210  <none>       80/TCP    3s
xrayed-giraffe-prometheus-kube-state-metrics  None          <none>       80/TCP    3s
xrayed-giraffe-prometheus-node-exporter       None          <none>       9100/TCP  3s
xrayed-giraffe-prometheus-pushgateway         10.0.29.114   <none>       9091/TCP  3s
xrayed-giraffe-prometheus-server              10.0.114.91   <none>       80/TCP    3s

==> v1beta1/DaemonSet
NAME                                     DESIRED  CURRENT  READY  UP-TO-DATE  AVAILABLE  NODE-SELECTOR  AGE
xrayed-giraffe-prometheus-node-exporter  1        1        0      1           0          <none>         2s

==> v1beta1/Deployment
NAME                                          DESIRED  CURRENT  UP-TO-DATE  AVAILABLE  AGE
xrayed-giraffe-prometheus-alertmanager        1        1        1           0          2s
xrayed-giraffe-prometheus-kube-state-metrics  1        1        1           0          2s
xrayed-giraffe-prometheus-pushgateway         1        1        1           0          2s
xrayed-giraffe-prometheus-server              1        1        1           0          2s

==> v1/ConfigMap
NAME                                    DATA  AGE
xrayed-giraffe-prometheus-alertmanager  1     3s
xrayed-giraffe-prometheus-server        3     3s

NOTES:
The Prometheus server can be accessed via port 80 on the following DNS name from within your cluster:
xrayed-giraffe-prometheus-server.default.svc.cluster.local

Get the Prometheus server URL by running these commands in the same shell:
  export POD_NAME=$(kubectl get pods --namespace default -l "app=prometheus,component=server" -o jsonpath="{.items[0].metadata.name}")
  kubectl --namespace default port-forward $POD_NAME 9090

The Prometheus alertmanager can be accessed via port 80 on the following DNS name from within your cluster:
xrayed-giraffe-prometheus-alertmanager.default.svc.cluster.local

Get the Alertmanager URL by running these commands in the same shell:
  export POD_NAME=$(kubectl get pods --namespace default -l "app=prometheus,component=alertmanager" -o jsonpath="{.items[0].metadata.name}")
  kubectl --namespace default port-forward $POD_NAME 9093

The Prometheus PushGateway can be accessed via port 9091 on the following DNS name from within your cluster:
xrayed-giraffe-prometheus-pushgateway.default.svc.cluster.local

Get the PushGateway URL by running these commands in the same shell:
  export POD_NAME=$(kubectl get pods --namespace default -l "app=prometheus,component=pushgateway" -o jsonpath="{.items[0].metadata.name}")
  kubectl --namespace default port-forward $POD_NAME 9093

For more information on running Prometheus, visit:
https://prometheus.io/

Output

$ kubectl get pods -o wide
NAME                                                           READY     STATUS              RESTARTS   AGE       IP            NODE
aci-connector-linux-virtual-kubelet-for-aks-2122567888-2nm9w   1/1       Running             0          3m        10.244.0.9    aks-nodepool1-34825167-0
xrayed-giraffe-prometheus-alertmanager-3617369642-m4jkm        0/2       Pending             0          9s        <none>        <none>
xrayed-giraffe-prometheus-kube-state-metrics-801971192-5xvb9   1/1       Running             0          9s        10.244.0.10   aks-nodepool1-34825167-0
xrayed-giraffe-prometheus-node-exporter-jj7wt                  1/1       Running             0          9s        10.240.0.4    aks-nodepool1-34825167-0
xrayed-giraffe-prometheus-pushgateway-407613393-7rkcc          0/1       ContainerCreating   0          9s        <none>        aks-nodepool1-34825167-0
xrayed-giraffe-prometheus-server-4184339985-6zr4c              0/2       Pending             0          9s        <none>        <none>

Is it possible to schedule all containers solely on ACI and get rid of the AKS nodes completely?

Thanks Omer