{"action":"created","issue":{"url":"https://api.github.com/repos/deis/router/issues/223","repository_url":"https://api.github.com/repos/deis/router","labels_url":"https://api.github.com/repos/deis/router/issues/223/labels{/name}","comments_url":"https://api.github.com/repos/deis/router/issues/223/comments","events_url":"https://api.github.com/repos/deis/router/issues/223/events","html_url":"https://github.com/deis/router/issues/223","id":169635325,"number":223,"title":"Routing only work with Type: LoadBalancer not with Type: NodePort","user":{"login":"pixeleet","id":5776997,"avatar_url":"https://avatars.githubusercontent.com/u/5776997?v=3","gravatar_id":"","url":"https://api.github.com/users/pixeleet","html_url":"https://github.com/pixeleet","followers_url":"https://api.github.com/users/pixeleet/followers","following_url":"https://api.github.com/users/pixeleet/following{/other_user}","gists_url":"https://api.github.com/users/pixeleet/gists{/gist_id}","starred_url":"https://api.github.com/users/pixeleet/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pixeleet/subscriptions","organizations_url":"https://api.github.com/users/pixeleet/orgs","repos_url":"https://api.github.com/users/pixeleet/repos","events_url":"https://api.github.com/users/pixeleet/events{/privacy}","received_events_url":"https://api.github.com/users/pixeleet/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":8,"created_at":"2016-08-05T15:37:32Z","updated_at":"2016-08-09T14:36:00Z","closed_at":null,"body":"I'm using the `router` standalone without workflow on AWS.\r\n\r\nI've managed to set up everything properly, SSL certificates work out of the box, happy happy joy joy!\r\n\r\nBut. If I provision the ELB with `Type`, `LoadBalancer` setting in the `Service`, it only gets attached to one of the two AZs, therefore I have to touch the config by hand to update it to have all AZs, and then add it to R53, so I've decided to put it into terraform.\r\n\r\nHowever, if I declare an ELB with the exact same settings as the Service would provision if I use `Type`, `LoadBalancer`, while using `Type: NodePort` the router will not resolve. \r\n\r\nWhat would be the cause to this? To my understanding configuring an ELB by hand (or terraform) to do the same thing should work, but then it doesn't. What am I missing here? \r\n\r\n"},"comment":{"url":"https://api.github.com/repos/deis/router/issues/comments/238573105","html_url":"https://github.com/deis/router/issues/223#issuecomment-238573105","issue_url":"https://api.github.com/repos/deis/router/issues/223","id":238573105,"user":{"login":"krancour","id":1821014,"avatar_url":"https://avatars.githubusercontent.com/u/1821014?v=3","gravatar_id":"","url":"https://api.github.com/users/krancour","html_url":"https://github.com/krancour","followers_url":"https://api.github.com/users/krancour/followers","following_url":"https://api.github.com/users/krancour/following{/other_user}","gists_url":"https://api.github.com/users/krancour/gists{/gist_id}","starred_url":"https://api.github.com/users/krancour/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/krancour/subscriptions","organizations_url":"https://api.github.com/users/krancour/orgs","repos_url":"https://api.github.com/users/krancour/repos","events_url":"https://api.github.com/users/krancour/events{/privacy}","received_events_url":"https://api.github.com/users/krancour/received_events","type":"User","site_admin":false},"created_at":"2016-08-09T14:36:00Z","updated_at":"2016-08-09T14:36:00Z","body":"I've done it by hand before. There's no internal magic either.\r\n\r\nCan you confirm you have followed these steps?\r\n\r\n1. Created new ELB having some security group, e.g. `MyK8sELB`\r\n1. Map listeners on ELB as follows:\r\n    * Listener: TCP/80; Backend: TCP/80\r\n    * Listener: TCP/443; Backend: TCP/443\r\n    * Listener: TCP/2222; Backend: TCP/2222\r\n    * Listener: TCP/9090; Backend: TCP/9090\r\n1. Add healthcheck:\r\n    * Port: 9090; Protocol: HTTP; Endpoint: /healthz\r\n1. Ensure k8s workers' security group permits ingress on all ports mentioned above from the ELB's security group.\r\n1. Have _all_ the k8s workers added to the backend pool.\r\n\r\nIf setup exactly as described, then take a look and see whether the ELB is regarding any of the worker nodes as healthy and in service. The _only_ nodes considered healthy should be _only_ the ones currently hosting a router pod. They would be the only ones to receive traffic. If router pod(s) should happen to shift around the cluster over time, the nodes that the ELB regards as healthy will change."}}
{"actor":{"display_login":"krancour"}}