{"action":"created","issue":{"url":"https://api.github.com/repos/mesosphere/mesos-dns/issues/62","labels_url":"https://api.github.com/repos/mesosphere/mesos-dns/issues/62/labels{/name}","comments_url":"https://api.github.com/repos/mesosphere/mesos-dns/issues/62/comments","events_url":"https://api.github.com/repos/mesosphere/mesos-dns/issues/62/events","html_url":"https://github.com/mesosphere/mesos-dns/issues/62","id":55118117,"number":62,"title":"support for plugins","user":{"login":"jdef","id":2348332,"avatar_url":"https://avatars.githubusercontent.com/u/2348332?v=3","gravatar_id":"","url":"https://api.github.com/users/jdef","html_url":"https://github.com/jdef","followers_url":"https://api.github.com/users/jdef/followers","following_url":"https://api.github.com/users/jdef/following{/other_user}","gists_url":"https://api.github.com/users/jdef/gists{/gist_id}","starred_url":"https://api.github.com/users/jdef/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jdef/subscriptions","organizations_url":"https://api.github.com/users/jdef/orgs","repos_url":"https://api.github.com/users/jdef/repos","events_url":"https://api.github.com/users/jdef/events{/privacy}","received_events_url":"https://api.github.com/users/jdef/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/mesosphere/mesos-dns/labels/enhancement","name":"enhancement","color":"84b6eb"},{"url":"https://api.github.com/repos/mesosphere/mesos-dns/labels/question","name":"question","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2015-01-22T06:12:07Z","updated_at":"2015-08-11T11:59:06Z","closed_at":null,"body":"I'm thinking of how I might bridge kubernetes service discovery and mesos service discovery. Part of a solution might be a mesos-dns \"plugin\" that watches the kubernetes service registry and manages DNS records for kubernetes services inside mesos-dns (so that mesos tasks using mesos-dns services for resolution can also see kubernetes services). The other half of a solution might be an additional kubernetes service endpoint controller that watches mesos tasks (like mesos-dns does) and manages kubernetes endpoint records (so that kubernetes pods can find mesos services hosted by other frameworks).\r\n\r\nAny thoughts re: a plugin model?"},"comment":{"url":"https://api.github.com/repos/mesosphere/mesos-dns/issues/comments/129849909","html_url":"https://github.com/mesosphere/mesos-dns/issues/62#issuecomment-129849909","issue_url":"https://api.github.com/repos/mesosphere/mesos-dns/issues/62","id":129849909,"user":{"login":"tsenart","id":67471,"avatar_url":"https://avatars.githubusercontent.com/u/67471?v=3","gravatar_id":"","url":"https://api.github.com/users/tsenart","html_url":"https://github.com/tsenart","followers_url":"https://api.github.com/users/tsenart/followers","following_url":"https://api.github.com/users/tsenart/following{/other_user}","gists_url":"https://api.github.com/users/tsenart/gists{/gist_id}","starred_url":"https://api.github.com/users/tsenart/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tsenart/subscriptions","organizations_url":"https://api.github.com/users/tsenart/orgs","repos_url":"https://api.github.com/users/tsenart/repos","events_url":"https://api.github.com/users/tsenart/events{/privacy}","received_events_url":"https://api.github.com/users/tsenart/received_events","type":"User","site_admin":false},"created_at":"2015-08-11T11:59:06Z","updated_at":"2015-08-11T11:59:06Z","body":"@jdef: Thanks for the info, makes sense.\r\n\r\nNow, I have some ideas and intuition that tell me all mesos-dns data sources should be modelled the exact same way, with a lean, well defined streaming interface (with channels). If we're going down the path of having different data sources, I don't see why mesos state should be treated in a special way."}}