Heapster service not found

[shayansarkar]

Is this a request for help?:
Yes

Is this an ISSUE or FEATURE REQUEST? (choose one):
Issue

What version of acs-engine?:
Version: canary
GitCommit: f8753ad

Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
Kubernetes 1.10.3

What happened:
I deployed a new cluster, and in the new cluster I ran the following command

kubectl top pods --all-namespaces

and I received the following error

Error from server (NotFound): the server could not find the requested resource (get services http:heapster:)

What you expected to happen:

I expected to see a list of pods running and the CPU and Memory usage

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

This is the json file i used for the creation of the cluster and then after it is deployed, I ran the kubectl top pods command.

{
  "apiVersion": "vlabs",
  "properties": {
    "orchestratorProfile": {
      "orchestratorType": "Kubernetes",
      "orchestratorVersion": "1.10.3",
      "kubernetesConfig": {
        "enableRbac": true,
        "dockerEngineVersion": "17.05.*",
        "addons": [
          {
            "name": "cluster-autoscaler",
            "enabled": true,
            "config": {
              "minNodes": "2",
              "maxNodes": "40"
            }
          }
        ]
      }
    },
    "masterProfile": {
      "count": 3,
      "dnsPrefix": "",
      "vmSize": "Standard_D2s_v3",
      "vnetSubnetId": "",
      "firstConsecutiveStaticIP": "",
      "vnetCidr": ""
    },
    "agentPoolProfiles": [
      {
        "name": "agentpool1",
        "count": 2,
        "vmSize": "Standard_E2s_v3",
        "availabilityProfile": "VirtualMachineScaleSets",
        "vnetSubnetId": "",
        "storageProfile": "ManagedDisks"
      }
    ],
    "linuxProfile": {
      "adminUsername": "",
      "ssh": {
        "publicKeys": [
          {
            "keyData":""
          }
        ]
      }
    },
    "servicePrincipalProfile": {
      "clientId": "",
      "secret": ""
    }
  }
}

Anything else we need to know:

[shayansarkar]

For some additional information and questions, it seems as though if I ssh into the master node and run

kubectl top pods --all-namespaces

it works as expected. However, if I run the same command from my machine, I still get the following message:
Error from server (NotFound): the server could not find the requested resource (get services http:heapster:)

If I create a cluster that does not use a custom VNet it also seems to work fine.

One thing I realized around setting up the custom VNet, according to the documentation at https://github.com/Azure/acs-engine/blob/master/docs/custom-vnet.md there should be a route table that I assign to the VNet subnet. However, it does not look like there is a route table generated for the cluster. Should there have been a route table generated?

[shayansarkar]

@ewok2030 your heapster update that got merged into master fixed my issue. Thanks for the fix!