{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes-sigs/aws-alb-ingress-controller/issues/473","repository_url":"https://api.github.com/repos/kubernetes-sigs/aws-alb-ingress-controller","labels_url":"https://api.github.com/repos/kubernetes-sigs/aws-alb-ingress-controller/issues/473/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes-sigs/aws-alb-ingress-controller/issues/473/comments","events_url":"https://api.github.com/repos/kubernetes-sigs/aws-alb-ingress-controller/issues/473/events","html_url":"https://github.com/kubernetes-sigs/aws-alb-ingress-controller/issues/473","id":343223625,"node_id":"MDU6SXNzdWUzNDMyMjM2MjU=","number":473,"title":"Documentation help with Service Annotations","user":{"login":"stvdilln","id":4500982,"node_id":"MDQ6VXNlcjQ1MDA5ODI=","avatar_url":"https://avatars3.githubusercontent.com/u/4500982?v=4","gravatar_id":"","url":"https://api.github.com/users/stvdilln","html_url":"https://github.com/stvdilln","followers_url":"https://api.github.com/users/stvdilln/followers","following_url":"https://api.github.com/users/stvdilln/following{/other_user}","gists_url":"https://api.github.com/users/stvdilln/gists{/gist_id}","starred_url":"https://api.github.com/users/stvdilln/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stvdilln/subscriptions","organizations_url":"https://api.github.com/users/stvdilln/orgs","repos_url":"https://api.github.com/users/stvdilln/repos","events_url":"https://api.github.com/users/stvdilln/events{/privacy}","received_events_url":"https://api.github.com/users/stvdilln/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-07-20T19:33:50Z","updated_at":"2018-07-26T17:17:51Z","closed_at":null,"author_association":"NONE","body":"We have a ingress controller with a few rules.  We have a Jenkins server that returns an error on url \"/\" so we are trying to get the health check to that service to \"/robots.txt\".  The Documentation says that you can override ingress settings via annotations in the service.  I do not think I have the annotations in the correct place, as they have no effect on the target group.  I've even put very invalid settings in like \"health-check-port: goober\" and I can't even force an error.  \r\nI've been through the two samples, and don't see a service annotation.  Not sure how this is supposed to work.\r\n\r\nHere is how I have tried to annotate the jenkins service:\r\n```\r\nsteved@steve-mint ~/projects/github/aws-alb-ingress-controller $ kubectl describe service jenkins\r\nName:                     jenkins\r\nNamespace:                default\r\nLabels:                   <none>\r\nAnnotations:              alb.ingress.kubernetes.io/healthcheck-path=/robots.txt\r\n                          field.cattle.io/publicEndpoints=[{\"port\":30317,\"protocol\":\"TCP\",\"serviceName\":\"default:jenkins\",\"allNodes\":true}]\r\nSelector:                 app=jenkins\r\nType:                     NodePort\r\nIP:                       172.20.32.249\r\nPort:                     <unset>  8080/TCP\r\nTargetPort:               8080/TCP\r\nNodePort:                 <unset>  30317/TCP\r\nEndpoints:                10.105.43.93:8080\r\nSession Affinity:         None\r\nExternal Traffic Policy:  Cluster\r\nEvents:                   <none>\r\n```\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/kubernetes-sigs/aws-alb-ingress-controller/issues/comments/408170134","html_url":"https://github.com/kubernetes-sigs/aws-alb-ingress-controller/issues/473#issuecomment-408170134","issue_url":"https://api.github.com/repos/kubernetes-sigs/aws-alb-ingress-controller/issues/473","id":408170134,"node_id":"MDEyOklzc3VlQ29tbWVudDQwODE3MDEzNA==","user":{"login":"stvdilln","id":4500982,"node_id":"MDQ6VXNlcjQ1MDA5ODI=","avatar_url":"https://avatars3.githubusercontent.com/u/4500982?v=4","gravatar_id":"","url":"https://api.github.com/users/stvdilln","html_url":"https://github.com/stvdilln","followers_url":"https://api.github.com/users/stvdilln/followers","following_url":"https://api.github.com/users/stvdilln/following{/other_user}","gists_url":"https://api.github.com/users/stvdilln/gists{/gist_id}","starred_url":"https://api.github.com/users/stvdilln/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stvdilln/subscriptions","organizations_url":"https://api.github.com/users/stvdilln/orgs","repos_url":"https://api.github.com/users/stvdilln/repos","events_url":"https://api.github.com/users/stvdilln/events{/privacy}","received_events_url":"https://api.github.com/users/stvdilln/received_events","type":"User","site_admin":false},"created_at":"2018-07-26T17:17:51Z","updated_at":"2018-07-26T17:17:51Z","author_association":"NONE","body":"@bigkraig Sheepishly I say 1.0-Alpha 3.  I was following example by pahud, and one of his yaml files was out of date when I deployed.  He's updated his demo instructions and I updated my controller to latest release.  I nuked the alb and let it rebuild, everything is working as expected.\r\nI don't know if the docs could use updating, If I had correct software it would have worked fine.  Probably just close as user-error.  But thanks for the help, I'm up and running!"}}
{"actor":{"display_login":"stvdilln"}}