{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/61497","repository_url":"https://api.github.com/repos/kubernetes/kubernetes","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/61497/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/61497/comments","events_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/61497/events","html_url":"https://github.com/kubernetes/kubernetes/issues/61497","id":307417677,"node_id":"MDU6SXNzdWUzMDc0MTc2Nzc=","number":61497,"title":"Job - Target existing Pod and Container to carry out command execution. ","user":{"login":"davissp14","id":423038,"node_id":"MDQ6VXNlcjQyMzAzOA==","avatar_url":"https://avatars3.githubusercontent.com/u/423038?v=4","gravatar_id":"","url":"https://api.github.com/users/davissp14","html_url":"https://github.com/davissp14","followers_url":"https://api.github.com/users/davissp14/followers","following_url":"https://api.github.com/users/davissp14/following{/other_user}","gists_url":"https://api.github.com/users/davissp14/gists{/gist_id}","starred_url":"https://api.github.com/users/davissp14/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/davissp14/subscriptions","organizations_url":"https://api.github.com/users/davissp14/orgs","repos_url":"https://api.github.com/users/davissp14/repos","events_url":"https://api.github.com/users/davissp14/events{/privacy}","received_events_url":"https://api.github.com/users/davissp14/received_events","type":"User","site_admin":false},"labels":[{"id":267761362,"node_id":"MDU6TGFiZWwyNjc3NjEzNjI=","url":"https://api.github.com/repos/kubernetes/kubernetes/labels/kind/feature","name":"kind/feature","color":"c7def8","default":false},{"id":778118402,"node_id":"MDU6TGFiZWw3NzgxMTg0MDI=","url":"https://api.github.com/repos/kubernetes/kubernetes/labels/lifecycle/rotten","name":"lifecycle/rotten","color":"604460","default":false},{"id":404091735,"node_id":"MDU6TGFiZWw0MDQwOTE3MzU=","url":"https://api.github.com/repos/kubernetes/kubernetes/labels/sig/apps","name":"sig/apps","color":"d2b48c","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2018-03-21T21:05:02Z","updated_at":"2018-09-08T17:34:45Z","closed_at":null,"author_association":"NONE","body":"/kind feature\r\n/sig api-machinery\r\n\r\nWe are hosting various databases within our stack that are spread across various Pods.  Within each Pod, we have two containers, the DB instance and a side-car container containing various DB specific mgmt scripts.  These scripts serve various purposes and some are long-lived and some are single quick on-demand queries that return data.\r\n\r\nWe have been considering using Jobs to communicate with the DB instance vs. having a permanent side-car container, however, the overhead of spinning up a completely new Pod with each execution seems like overkill.    \r\n\r\nHas any consideration been given to provide Jobs more flexibility around where the actual execution should take place?  \r\n\r\nExample:  Instead of building out a completely new Pod to execute a simple one-liner, I'd love to be able to target a specific pod and container to carry out a given task. \r\n\r\nThoughts?"},"comment":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/comments/419659968","html_url":"https://github.com/kubernetes/kubernetes/issues/61497#issuecomment-419659968","issue_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/61497","id":419659968,"node_id":"MDEyOklzc3VlQ29tbWVudDQxOTY1OTk2OA==","user":{"login":"k8s-ci-robot","id":20407524,"node_id":"MDQ6VXNlcjIwNDA3NTI0","avatar_url":"https://avatars0.githubusercontent.com/u/20407524?v=4","gravatar_id":"","url":"https://api.github.com/users/k8s-ci-robot","html_url":"https://github.com/k8s-ci-robot","followers_url":"https://api.github.com/users/k8s-ci-robot/followers","following_url":"https://api.github.com/users/k8s-ci-robot/following{/other_user}","gists_url":"https://api.github.com/users/k8s-ci-robot/gists{/gist_id}","starred_url":"https://api.github.com/users/k8s-ci-robot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/k8s-ci-robot/subscriptions","organizations_url":"https://api.github.com/users/k8s-ci-robot/orgs","repos_url":"https://api.github.com/users/k8s-ci-robot/repos","events_url":"https://api.github.com/users/k8s-ci-robot/events{/privacy}","received_events_url":"https://api.github.com/users/k8s-ci-robot/received_events","type":"User","site_admin":false},"created_at":"2018-09-08T17:34:45Z","updated_at":"2018-09-08T17:34:45Z","author_association":"NONE","body":"@fejta-bot: Closing this issue.\n\n<details>\n\nIn response to [this](https://github.com/kubernetes/kubernetes/issues/61497#issuecomment-419659962):\n\n>Rotten issues close after 30d of inactivity.\n>Reopen the issue with `/reopen`.\n>Mark the issue as fresh with `/remove-lifecycle rotten`.\n>\n>Send feedback to sig-testing, kubernetes/test-infra and/or [fejta](https://github.com/fejta).\n>/close\n\n\nInstructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.\n</details>"}}
{"actor":{"display_login":"k8s-ci-robot"}}