search

k8s-cookbook / recipes

Kubernetes Cookbook
http://k8s.cookbook.fyi
Apache License 2.0
169 stars 89 forks source link

Recipe 12.9 Managing etcd #11

Open bennybhlin opened 6 years ago

bennybhlin commented 6 years ago

With etcd 3.2.24 in my Kubernetes 1.12 cluster, when I used 'curl localhost:2379/v2/keys/registry', result is empty.

From comment of this recipe I knew that newer Kubernetes is using etcd3 and probably etcd v3 API, however, even I tried to use 'curl localhost:2379/v3/keys/registry', still I got no output.

Is there any other things changed which readers should know?

bennybhlin commented 6 years ago

Correction, my etcd3 is still using API v2

default

mhausenblas commented 6 years ago

@bennybhlin I will repeat it again: we're using 1.7 in the book and all recipes are against this version. Having said this, I'll earmark this issue to remind ourselves to update this recipe in a potential new edition of the book and for now, if you follow this blog post you should get by?

mhausenblas commented 6 years ago

@bennybhlin I've added you as a collaborator to this repo now so you can assign the enhancement label to issues you think should be addressed in a new version of the book. We will then select the ones for respective milestone.

bennybhlin commented 6 years ago

Hahaha, sure Michael; all I want to do is to clarify any possible difference for readers, and tell them in my comments how to get rid of any error caused by difference. No offence.

It's close to the end of my own examples review; I promise you won't be bothered by me again for just a few more days :-D

mhausenblas commented 6 years ago

Quite the opposite, @bennybhlin it's much appreciated what you're doing here and certainly deserves kudos in the new revision of the book, it's just not much we can do (in the book) right now, only here on the repo ;)

So, please keep it coming, just want to manage expectations.

mhausenblas commented 6 years ago

Also, we should keep all issues open that we want to have addressed in the upcoming book revision. With the label and the milestone we should be in a good position to address them rather easily.

sebgoa commented 6 years ago

Hum, we need to check this again, because latest version have etcd over TLS so you can talk to it straightup like this, you need to pass the certs.

bennybhlin commented 6 years ago

Using this way still got no effect.

$ curl --cacert /etc/kubernetes/pki/ca.crt https://127.0.0.1:2379/v2/keys/registry curl: (35) gnutls_handshake() failed: Certificate is bad