With etcd 2+ with the following command I was able to inspect the apiserver 
state.

$etcdctl ls --recursive /registry
/registry/clusterroles
/registry/clusterroles/system:controller:daemon-set-controller
...
/registry/daemonsets
/registry/daemonsets/default
/registry/daemonsets/kube-system
/registry/daemonsets/kube-system/keepalived
/registry/daemonsets/kube-system/nghttpx-ingress-lb
/registry/minions
/registry/minions/10.10.2.102
/registry/minions/10.10.3.101
/registry/minions/10.10.3.102
/registry/minions/10.10.3.103
/registry/minions/10.10.3.104
...

With etcd 3+ i am struggling to find the apiserver state. The same command 
delivers empty output. This was useful when viewing raw state like TPRs if 
you did not have the TPR locally.

kind regards,

-- 
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.
  • [kubernetes-user... 'mrpanigale' via Kubernetes user discussion and Q&A
    • Re: [kubern... 'Daniel Smith' via Kubernetes user discussion and Q&A
      • Re: [ku... 'Joe Betz' via Kubernetes user discussion and Q&A

Reply via email to