{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/24957","repository_url":"https://api.github.com/repos/kubernetes/kubernetes","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/24957/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/24957/comments","events_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/24957/events","html_url":"https://github.com/kubernetes/kubernetes/issues/24957","id":151777021,"number":24957,"title":"Feature request: A way to signal pods","user":{"login":"thockin","id":5595220,"avatar_url":"https://avatars.githubusercontent.com/u/5595220?v=3","gravatar_id":"","url":"https://api.github.com/users/thockin","html_url":"https://github.com/thockin","followers_url":"https://api.github.com/users/thockin/followers","following_url":"https://api.github.com/users/thockin/following{/other_user}","gists_url":"https://api.github.com/users/thockin/gists{/gist_id}","starred_url":"https://api.github.com/users/thockin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/thockin/subscriptions","organizations_url":"https://api.github.com/users/thockin/orgs","repos_url":"https://api.github.com/users/thockin/repos","events_url":"https://api.github.com/users/thockin/events{/privacy}","received_events_url":"https://api.github.com/users/thockin/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/area/api","name":"area/api","color":"e1ed21"},{"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/kind/feature","name":"kind/feature","color":"c7def8"},{"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/team/node","name":"team/node","color":"d2b48c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":29,"created_at":"2016-04-29T01:22:14Z","updated_at":"2016-06-09T13:13:24Z","closed_at":null,"body":"This has come up a bunch of times in conversations.  The idea is that some external orchestration is being performed and the user needs to signal (SIGHUP usually, but arbitrary) pods.  Sometimes this is related to ConfigMap (#22368) and sometimes not.  This also can be used to \"bounce\" pods.\r\n\r\nWe can't currently signal across containers in a pod, so any sort of sidecar is out for now.\r\n\r\nWe can do it by `docker kill`, but something like `kubectl signal` is clumsy - it's not clearly an API operation (unless we revisit\r\n'operation' constructs for managing imperative async actions).\r\n\r\nAnother issue is that a pod doesn't really exist - do we signal one container?  Which one?  Maybe all containers?  Or do we nominate a signalee in the pod spec?"},"comment":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/comments/224890183","html_url":"https://github.com/kubernetes/kubernetes/issues/24957#issuecomment-224890183","issue_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/24957","id":224890183,"user":{"login":"smarterclayton","id":1163175,"avatar_url":"https://avatars.githubusercontent.com/u/1163175?v=3","gravatar_id":"","url":"https://api.github.com/users/smarterclayton","html_url":"https://github.com/smarterclayton","followers_url":"https://api.github.com/users/smarterclayton/followers","following_url":"https://api.github.com/users/smarterclayton/following{/other_user}","gists_url":"https://api.github.com/users/smarterclayton/gists{/gist_id}","starred_url":"https://api.github.com/users/smarterclayton/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/smarterclayton/subscriptions","organizations_url":"https://api.github.com/users/smarterclayton/orgs","repos_url":"https://api.github.com/users/smarterclayton/repos","events_url":"https://api.github.com/users/smarterclayton/events{/privacy}","received_events_url":"https://api.github.com/users/smarterclayton/received_events","type":"User","site_admin":false},"created_at":"2016-06-09T13:13:24Z","updated_at":"2016-06-09T13:13:24Z","body":"I think both @bprashanth and I were suggesting pod or container defined named hooks at various points that were then treated as one or more \"signals\", and that's not terribly different from what's being proposed.  If a pod author wanted to create:\r\n\r\n```\r\nnotification:\r\n  - name: bump\r\n    signal: SIGUSR1\r\n```\r\n\r\nthat's both intentional and extensible, as you note.\r\n\r\nI don't think there's an \"event bus\" per se, but we do need to talk about delivery guarantees.  As a client author I should not have to write a retry loop around notifications."}}
{"actor":{"display_login":"smarterclayton"}}