{"action":"created","issue":{"url":"https://api.github.com/repos/GoogleCloudPlatform/kubernetes/issues/3317","labels_url":"https://api.github.com/repos/GoogleCloudPlatform/kubernetes/issues/3317/labels{/name}","comments_url":"https://api.github.com/repos/GoogleCloudPlatform/kubernetes/issues/3317/comments","events_url":"https://api.github.com/repos/GoogleCloudPlatform/kubernetes/issues/3317/events","html_url":"https://github.com/GoogleCloudPlatform/kubernetes/issues/3317","id":53762749,"number":3317,"title":"Avoiding accidental Elasticsearch cluster formations in same namespace or cluster","user":{"login":"satnam6502","id":6164339,"avatar_url":"https://avatars.githubusercontent.com/u/6164339?v=3","gravatar_id":"","url":"https://api.github.com/users/satnam6502","html_url":"https://github.com/satnam6502","followers_url":"https://api.github.com/users/satnam6502/followers","following_url":"https://api.github.com/users/satnam6502/following{/other_user}","gists_url":"https://api.github.com/users/satnam6502/gists{/gist_id}","starred_url":"https://api.github.com/users/satnam6502/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/satnam6502/subscriptions","organizations_url":"https://api.github.com/users/satnam6502/orgs","repos_url":"https://api.github.com/users/satnam6502/repos","events_url":"https://api.github.com/users/satnam6502/events{/privacy}","received_events_url":"https://api.github.com/users/satnam6502/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-01-08T15:32:00Z","updated_at":"2015-01-08T17:04:44Z","closed_at":null,"body":"Fluentd logging is being changed to refer to Elasticsearch with DNS (`elasticsearch.default`) and there is also an instance of Elasticsearch that is used for monitoring (but this currently does not use DNS). If we run Elasticsearch instances in the same namespace then I think they will 'interfere' with each other i.e. by default form a cluster.\r\n\r\nWe should be aware of this. I think we should either decide to use shared Elasticsearch clusters for things like logging and monitoring and put them in an appropriate namespace [I am not sure if this is what we really want to do] or we should be careful to put different distinct Elasticsearch clusters into different namespaces. So, for example, instead of `elasticsearch.default` we should perhaps use `elasticsearch.logging` and likewise for monitoring if there is every a need to move it over to DNS e.g. `elasticsearch.monitoring`. \r\n\r\n@vmarmol @vishh "},"comment":{"url":"https://api.github.com/repos/GoogleCloudPlatform/kubernetes/issues/comments/69211288","html_url":"https://github.com/GoogleCloudPlatform/kubernetes/issues/3317#issuecomment-69211288","issue_url":"https://api.github.com/repos/GoogleCloudPlatform/kubernetes/issues/3317","id":69211288,"user":{"login":"satnam6502","id":6164339,"avatar_url":"https://avatars.githubusercontent.com/u/6164339?v=3","gravatar_id":"","url":"https://api.github.com/users/satnam6502","html_url":"https://github.com/satnam6502","followers_url":"https://api.github.com/users/satnam6502/followers","following_url":"https://api.github.com/users/satnam6502/following{/other_user}","gists_url":"https://api.github.com/users/satnam6502/gists{/gist_id}","starred_url":"https://api.github.com/users/satnam6502/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/satnam6502/subscriptions","organizations_url":"https://api.github.com/users/satnam6502/orgs","repos_url":"https://api.github.com/users/satnam6502/repos","events_url":"https://api.github.com/users/satnam6502/events{/privacy}","received_events_url":"https://api.github.com/users/satnam6502/received_events","type":"User","site_admin":false},"created_at":"2015-01-08T17:04:44Z","updated_at":"2015-01-08T17:04:44Z","body":"OK, I'll close this issue for now. But at some point we might like to think about how cluster forming services like Elasticsearch interact with replication controllers and make sure that everything works together well and to establish any best practices. The logging work is likely to drive some of this anyway as we move to using multiple Elasticsearch instances for ingesting the logs from large clusters."}}