Thanks Daniel, that makes perfect sense - glad to have clarification! Michael
On Tue, May 2, 2017 at 4:27 PM, 'Daniel Smith' via Kubernetes user discussion and Q&A <kubernetes-users@googlegroups.com> wrote: > Sorry, but the backend storage used by Kubernetes in GKE is not exposed, > and there are no plans to expose it in the future. > > Even if you do have direct access to etcd, I'd strongly recommend using > the Kubernetes API for acquiring information like this. The API has various > backwards compatibility guarantees, which do not apply to the storage > layer. E.g., we just switched to etcd3, and soon we'll be doing a flag flip > and start writing a binary data format. > > The other concern of course is that access to etcd == root on the cluster. > > > > On Tue, May 2, 2017 at 9:54 AM, Michael Strickland < > michael.strickl...@nytimes.com> wrote: > >> Hello, I'm wondering if it's possible to access the etcd API from within >> a container running on Google Kubernetes Engine. >> >> We're using DataDog's docker-dd-agent image to monitor metrics in the >> cluster, and one feature is automatic service discovery >> <https://github.com/DataDog/docker-dd-agent#service-discovery> of >> containers deployed in the cluster. The agent does this by querying the >> etcd API for a cluster to discover containers matching certain names. >> >> On our previous self-managed Kubernetes cluster, we could access this API >> by querying localhost:4001 on our worker nodes. However, there doesn't >> appear to be a direct equivalent to that on GKE, as the etcd cluster is a >> managed service. >> >> Is there any way to interact with etcd within a cluster, or is the API >> intentionally closed off? >> >> Thanks! >> Michael >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Kubernetes user discussion and Q&A" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to kubernetes-users+unsubscr...@googlegroups.com. >> To post to this group, send email to kubernetes-users@googlegroups.com. >> Visit this group at https://groups.google.com/group/kubernetes-users. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Kubernetes user discussion and Q&A" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/kubernetes-users/6BLcAQAvPCU/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > kubernetes-users+unsubscr...@googlegroups.com. > To post to this group, send email to kubernetes-users@googlegroups.com. > Visit this group at https://groups.google.com/group/kubernetes-users. > For more options, visit https://groups.google.com/d/optout. > -- Michael Strickland Senior Developer, Interactive News The New York Times x7564 +1 434-760-3896 -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
