{"action":"opened","issue":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/61888","repository_url":"https://api.github.com/repos/kubernetes/kubernetes","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/61888/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/61888/comments","events_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/61888/events","html_url":"https://github.com/kubernetes/kubernetes/issues/61888","id":309708519,"number":61888,"title":"Support pulling from registry withing Kubernetes cluster","user":{"login":"amouat","id":246775,"avatar_url":"https://avatars3.githubusercontent.com/u/246775?v=4","gravatar_id":"","url":"https://api.github.com/users/amouat","html_url":"https://github.com/amouat","followers_url":"https://api.github.com/users/amouat/followers","following_url":"https://api.github.com/users/amouat/following{/other_user}","gists_url":"https://api.github.com/users/amouat/gists{/gist_id}","starred_url":"https://api.github.com/users/amouat/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/amouat/subscriptions","organizations_url":"https://api.github.com/users/amouat/orgs","repos_url":"https://api.github.com/users/amouat/repos","events_url":"https://api.github.com/users/amouat/events{/privacy}","received_events_url":"https://api.github.com/users/amouat/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-03-29T10:51:08Z","updated_at":"2018-03-29T10:51:08Z","closed_at":null,"author_association":"NONE","body":"<!-- This form is for bug reports and feature requests ONLY! \r\n\r\nIf you're looking for help check [Stack Overflow](https://stackoverflow.com/questions/tagged/kubernetes) and the [troubleshooting guide](https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/).\r\n-->\r\n\r\n**Is this a BUG REPORT or FEATURE REQUEST?**:\r\n\r\n> Uncomment only one, leave it on its own line: \r\n>\r\n> /kind bug\r\n/kind feature\r\n\r\n\r\n**What happened**:\r\nWith some work, it's possible to get a private registry running inside a Kubernetes cluster. However, it's annoyingly difficult to get Kubernetes to use the registry as pulls happen *outside* the cluster network. For example if I run a registry and expose via an service under the name \"k8s-registry\" on port 5000, the following will not work (ignoring certs for the minute):\r\n\r\n`kubectl run test --image k8s-registry:5000/myimage:bla`\r\n\r\nAs the node is not connected to the kubernetes DNS.\r\n\r\nFurther, if we hack k8s (e.g. by adding an entry to /etc/hosts on the nodes) to recognise the service name, we will still hit an issue with certificates, even if the registry uses a cert from the k8s CA (the k8s CA cert is not added to the node).\r\n\r\n**What you expected to happen**:\r\n\r\nIt would be great if pulls could be done using k8s services. This would either mean adding k8s DNS and the k8s CA cert to the nodes, or running pulls inside a pod. \r\n\r\n**How to reproduce it (as minimally and precisely as possible)**:\r\n\r\n\r\n**Anything else we need to know?**:\r\n\r\n**Environment**:\r\n- Kubernetes version (use `kubectl version`):\r\n- Cloud provider or hardware configuration:\r\n- OS (e.g. from /etc/os-release):\r\n- Kernel (e.g. `uname -a`):\r\n- Install tools:\r\n- Others:\r\n"}}
{"actor":{"display_login":"amouat"}}