{"action":"created","issue":{"url":"https://api.github.com/repos/docker/for-aws/issues/83","repository_url":"https://api.github.com/repos/docker/for-aws","labels_url":"https://api.github.com/repos/docker/for-aws/issues/83/labels{/name}","comments_url":"https://api.github.com/repos/docker/for-aws/issues/83/comments","events_url":"https://api.github.com/repos/docker/for-aws/issues/83/events","html_url":"https://github.com/docker/for-aws/issues/83","id":246384653,"number":83,"title":"Add Support for the Application Load Balancer (ELB v2)","user":{"login":"RehanSaeed","id":2270364,"avatar_url":"https://avatars2.githubusercontent.com/u/2270364?v=4","gravatar_id":"","url":"https://api.github.com/users/RehanSaeed","html_url":"https://github.com/RehanSaeed","followers_url":"https://api.github.com/users/RehanSaeed/followers","following_url":"https://api.github.com/users/RehanSaeed/following{/other_user}","gists_url":"https://api.github.com/users/RehanSaeed/gists{/gist_id}","starred_url":"https://api.github.com/users/RehanSaeed/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/RehanSaeed/subscriptions","organizations_url":"https://api.github.com/users/RehanSaeed/orgs","repos_url":"https://api.github.com/users/RehanSaeed/repos","events_url":"https://api.github.com/users/RehanSaeed/events{/privacy}","received_events_url":"https://api.github.com/users/RehanSaeed/received_events","type":"User","site_admin":false},"labels":[{"id":522008390,"url":"https://api.github.com/repos/docker/for-aws/labels/area/aws","name":"area/aws","color":"bfd4f2","default":false},{"id":522008671,"url":"https://api.github.com/repos/docker/for-aws/labels/kind/enhancement","name":"kind/enhancement","color":"e99695","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":14,"created_at":"2017-07-28T15:39:32Z","updated_at":"2018-04-08T10:46:49Z","closed_at":null,"author_association":"NONE","body":"The current cloud formation template creates a Classic load balancer (ELB v1). The newer Application Load Balancer (ELB v2) has the ability to route HTTP requests. I'd like to be able to do the following:\r\n\r\n> https://example.com --> Application Load Balancer (ELB v2) --> http://my-docker-service:5000\r\n\r\nWhat is the current recommended approach to do the above? I can think of a few options:\r\n\r\n1. What happens if I delete or turn off the Classic Load Balancer and create an Application Load Balancer in it's place. I'm assuming this would be bad and an upgrade of the cloud formation template would undo my change.\r\n2. Use an nginx container.\r\n3. Create an Application Load Balancer and point it at the Classic Load Balancer. This is not ideal from a cost and complexity perspective."},"comment":{"url":"https://api.github.com/repos/docker/for-aws/issues/comments/379540386","html_url":"https://github.com/docker/for-aws/issues/83#issuecomment-379540386","issue_url":"https://api.github.com/repos/docker/for-aws/issues/83","id":379540386,"user":{"login":"0v3rst33r","id":16577884,"avatar_url":"https://avatars2.githubusercontent.com/u/16577884?v=4","gravatar_id":"","url":"https://api.github.com/users/0v3rst33r","html_url":"https://github.com/0v3rst33r","followers_url":"https://api.github.com/users/0v3rst33r/followers","following_url":"https://api.github.com/users/0v3rst33r/following{/other_user}","gists_url":"https://api.github.com/users/0v3rst33r/gists{/gist_id}","starred_url":"https://api.github.com/users/0v3rst33r/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/0v3rst33r/subscriptions","organizations_url":"https://api.github.com/users/0v3rst33r/orgs","repos_url":"https://api.github.com/users/0v3rst33r/repos","events_url":"https://api.github.com/users/0v3rst33r/events{/privacy}","received_events_url":"https://api.github.com/users/0v3rst33r/received_events","type":"User","site_admin":false},"created_at":"2018-04-08T10:46:49Z","updated_at":"2018-04-08T10:46:49Z","author_association":"NONE","body":"@seriousben (and others) - hopefully my question is relevant enough to post here, please advise otherwise:\r\n\r\nCurrently I am using websockets with normal ELB/TCP:\r\n\r\n`Traffic -> ELB -> Nginx -> NodeJS service (using 'ws' npm pkg)`\r\n\r\nQuite often I see in the server logs\r\n```\r\nerror WebSocket is not open: readyState 3 (CLOSED)\r\n```\r\nand the client not knowing that the connection is in fact closed.  Am still in the process of properly debugging this, but I have heard advice that ALB (instead of Classic ELB) will make this problem go away with the way it persists connections, but wouldn't adding the `ping` from the server also make the connection a bit more stable (or better chance of staying persistent) whilst still using Classic ELB?\r\n\r\nSidenote:  the typical usage of this websocket connection is from a mobile client primarily being used when not on WIFI."}}
{"actor":{"display_login":"0v3rst33r"}}