{"action":"created","issue":{"url":"https://api.github.com/repos/30x/enrober/issues/65","repository_url":"https://api.github.com/repos/30x/enrober","labels_url":"https://api.github.com/repos/30x/enrober/issues/65/labels{/name}","comments_url":"https://api.github.com/repos/30x/enrober/issues/65/comments","events_url":"https://api.github.com/repos/30x/enrober/issues/65/events","html_url":"https://github.com/30x/enrober/issues/65","id":177533115,"number":65,"title":"Implement a cache for validating unique hostnames","user":{"login":"whitlockjc","id":98899,"avatar_url":"https://avatars.githubusercontent.com/u/98899?v=3","gravatar_id":"","url":"https://api.github.com/users/whitlockjc","html_url":"https://github.com/whitlockjc","followers_url":"https://api.github.com/users/whitlockjc/followers","following_url":"https://api.github.com/users/whitlockjc/following{/other_user}","gists_url":"https://api.github.com/users/whitlockjc/gists{/gist_id}","starred_url":"https://api.github.com/users/whitlockjc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/whitlockjc/subscriptions","organizations_url":"https://api.github.com/users/whitlockjc/orgs","repos_url":"https://api.github.com/users/whitlockjc/repos","events_url":"https://api.github.com/users/whitlockjc/events{/privacy}","received_events_url":"https://api.github.com/users/whitlockjc/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-09-16T22:28:38Z","updated_at":"2016-09-17T00:45:41Z","closed_at":null,"body":"Whenever an environment is created, we search for all namespaces and then check the `hostNames` to see if the new environment's `hostNames` are unique.  This will not scale very well and we should consider a cache somewhere.  _(I say \"somewhere\" because it could start out here but end up in some admission controller or namespace watcher controller.)_"},"comment":{"url":"https://api.github.com/repos/30x/enrober/issues/comments/247738552","html_url":"https://github.com/30x/enrober/issues/65#issuecomment-247738552","issue_url":"https://api.github.com/repos/30x/enrober/issues/65","id":247738552,"user":{"login":"mpnally","id":2752746,"avatar_url":"https://avatars.githubusercontent.com/u/2752746?v=3","gravatar_id":"","url":"https://api.github.com/users/mpnally","html_url":"https://github.com/mpnally","followers_url":"https://api.github.com/users/mpnally/followers","following_url":"https://api.github.com/users/mpnally/following{/other_user}","gists_url":"https://api.github.com/users/mpnally/gists{/gist_id}","starred_url":"https://api.github.com/users/mpnally/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mpnally/subscriptions","organizations_url":"https://api.github.com/users/mpnally/orgs","repos_url":"https://api.github.com/users/mpnally/repos","events_url":"https://api.github.com/users/mpnally/events{/privacy}","received_events_url":"https://api.github.com/users/mpnally/received_events","type":"User","site_admin":false},"created_at":"2016-09-17T00:45:40Z","updated_at":"2016-09-17T00:45:40Z","body":"When (if) we convert to the permissions service, this problem will go away.\nThe hostnames will be secured resources, and the permissions service will\nnot let you use it if someone else has it, unless they have said it's OK\nfor you to share. This is better than a cache, because it allows multiple\nnamespaces to share the same hosts (as we do/did with the 'apigee' and\n'shipyard' namespaces) but only if permission has been granted.\n\nMartin\n\nOn Fri, Sep 16, 2016 at 3:28 PM, Jeremy Whitlock <notifications@github.com>\nwrote:\n\n> Whenever an environment is created, we search for all namespaces and then\n> check the hostNames to see if the new environment's hostNames are unique.\n> This will not scale very well and we should consider a cache somewhere. *(I\n> say \"somewhere\" because it could start out here but end up in some\n> admission controller or namespace watcher controller.)*\n>\n> —\n> You are receiving this because you are subscribed to this thread.\n> Reply to this email directly, view it on GitHub\n> <https://github.com/30x/enrober/issues/65>, or mute the thread\n> <https://github.com/notifications/unsubscribe-auth/ACoA6nyh684rniPNrHMxLKfXcMREh2kwks5qqxgXgaJpZM4J_Z14>\n> .\n>\n\n\n\n-- \n\nMartin Nally, Apigee Engineering\n"}}
{"actor":{"display_login":"mpnally"}}