{"action":"created","issue":{"url":"https://api.github.com/repos/virtual-kubelet/virtual-kubelet/issues/154","repository_url":"https://api.github.com/repos/virtual-kubelet/virtual-kubelet","labels_url":"https://api.github.com/repos/virtual-kubelet/virtual-kubelet/issues/154/labels{/name}","comments_url":"https://api.github.com/repos/virtual-kubelet/virtual-kubelet/issues/154/comments","events_url":"https://api.github.com/repos/virtual-kubelet/virtual-kubelet/issues/154/events","html_url":"https://github.com/virtual-kubelet/virtual-kubelet/issues/154","id":317155477,"node_id":"MDU6SXNzdWUzMTcxNTU0Nzc=","number":154,"title":"Azure AKS virtual-kubelet pod gets an public ip instead of a cluster ip","user":{"login":"arjanschaaf","id":11680211,"node_id":"MDQ6VXNlcjExNjgwMjEx","avatar_url":"https://avatars0.githubusercontent.com/u/11680211?v=4","gravatar_id":"","url":"https://api.github.com/users/arjanschaaf","html_url":"https://github.com/arjanschaaf","followers_url":"https://api.github.com/users/arjanschaaf/followers","following_url":"https://api.github.com/users/arjanschaaf/following{/other_user}","gists_url":"https://api.github.com/users/arjanschaaf/gists{/gist_id}","starred_url":"https://api.github.com/users/arjanschaaf/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/arjanschaaf/subscriptions","organizations_url":"https://api.github.com/users/arjanschaaf/orgs","repos_url":"https://api.github.com/users/arjanschaaf/repos","events_url":"https://api.github.com/users/arjanschaaf/events{/privacy}","received_events_url":"https://api.github.com/users/arjanschaaf/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2018-04-24T10:01:27Z","updated_at":"2018-07-26T17:58:01Z","closed_at":null,"author_association":"NONE","body":"---\r\n\r\n### Environment summary\r\n\r\nProvider (e.g. Azure, Hyper)\r\n\r\nAzure\r\n\r\nVersion (e.g. 0.1, 0.2-beta)\r\n\r\nvirtual-kubelet-for-aks-0.1.3\r\n\r\nK8s Master Info (e.g. AKS, ACS, Bare Metal)\r\n\r\nAKS\r\n\r\nInstall Method (e.g. Helm Chart, )\r\n\r\nHelm Chart\r\n\r\n### Issue Details\r\n\r\nAfter deploying a single pod on the virtual-kubelet node in my environment, I wanted to go a couple of steps further. I wanted to create a kubernetes deployment + kubernetes service + kubernetes ingress. That way the actual pod deployed on the virtual-kubelet node by my deployment would be exposed by the NGINX Ingress Controller currently running in my AKS kubernetes cluster.\r\nI successfully created the deployment and a pod was started on the virtual-kubelet node. Only to my suprise the pod was given a public ip instead of an ip that is private to the kubernetes cluster (which it would get if this pod was deployed on a \"normal\" kubernetes node) and although the pod reported *ready* the replicaset never sees the pod as *ready*. Therefore it isn't registered with the service as a healthy endpoint and consequently the Ingress isn't going to work.\r\n\r\n```\r\nkubectl get replicaset\r\nNAME                 DESIRED   CURRENT   READY     AGE\r\nhttp-svc-597cdc956   1         1         0         39m\r\n```\r\n\r\n```\r\nkubectl get pod\r\nNAME                       READY     STATUS    RESTARTS   AGE\r\nhttp-svc-597cdc956-m9rkn   1/1       Running   0          39m\r\n```\r\n\r\nHow do I get a kubernetes deployment/replicaset to work while deploying on virutal-kubelet?\r\n\r\n### Repo Steps\r\n\r\n1) Create deployment\r\n2) See pod being started and becoming ready\r\n3) See that the replicaset / deployment never sees the replica (pod) as ready\r\n"},"comment":{"url":"https://api.github.com/repos/virtual-kubelet/virtual-kubelet/issues/comments/408182246","html_url":"https://github.com/virtual-kubelet/virtual-kubelet/issues/154#issuecomment-408182246","issue_url":"https://api.github.com/repos/virtual-kubelet/virtual-kubelet/issues/154","id":408182246,"node_id":"MDEyOklzc3VlQ29tbWVudDQwODE4MjI0Ng==","user":{"login":"jbenettius","id":21316675,"node_id":"MDQ6VXNlcjIxMzE2Njc1","avatar_url":"https://avatars2.githubusercontent.com/u/21316675?v=4","gravatar_id":"","url":"https://api.github.com/users/jbenettius","html_url":"https://github.com/jbenettius","followers_url":"https://api.github.com/users/jbenettius/followers","following_url":"https://api.github.com/users/jbenettius/following{/other_user}","gists_url":"https://api.github.com/users/jbenettius/gists{/gist_id}","starred_url":"https://api.github.com/users/jbenettius/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jbenettius/subscriptions","organizations_url":"https://api.github.com/users/jbenettius/orgs","repos_url":"https://api.github.com/users/jbenettius/repos","events_url":"https://api.github.com/users/jbenettius/events{/privacy}","received_events_url":"https://api.github.com/users/jbenettius/received_events","type":"User","site_admin":false},"created_at":"2018-07-26T17:58:01Z","updated_at":"2018-07-26T17:58:01Z","author_association":"NONE","body":"Is there an ETA yet for VNet support with ACI?"}}
{"actor":{"display_login":"jbenettius"}}