You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to support k3s backend change (eg: from mysql to postgres), we need to provide an etcd cli and cli configuration targetting the kine endpoint.
In order to support k3s backend change (eg: from mysql to embedded etcd), I need to leverage an etcd cli and cli configuration targetting the k3s embedded etcd cluster.
ls -al /var/vcap/store/k3s-server/server/tls/etcd/
total 48
drwx------ 2 root root 4096 Oct 4 19:58 .
drwx------ 4 root root 4096 Oct 4 19:58 ..
-rw-r--r-- 1 root root 1140 Oct 4 19:58 client.crt
-rw------- 1 root root 227 Oct 4 19:58 client.key
-rw------- 1 root root 566 Oct 4 19:53 peer-ca.crt
-rw------- 1 root root 227 Oct 4 19:53 peer-ca.key
-rw-r--r-- 1 root root 1352 Oct 4 19:58 peer-server-client.crt
-rw------- 1 root root 227 Oct 4 19:58 peer-server-client.key
-rw------- 1 root root 570 Oct 4 19:53 server-ca.crt
-rw------- 1 root root 227 Oct 4 19:53 server-ca.key
-rw-r--r-- 1 root root 1364 Oct 4 19:58 server-client.crt
-rw------- 1 root root 227 Oct 4 19:58 server-client.key
Workaround for missing etcdctl cli on the bosh release
# Use etcdctl with bosh specific paths # Display cluster status
ETCDCTL_ENDPOINTS='https://127.0.0.1:2379/' ETCDCTL_CACERT='/var/vcap/store/k3s-server/server/tls/etcd/server-ca.crt' ETCDCTL_CERT='/var/vcap/store/k3s-server/server/tls/etcd/server-client.crt' ETCDCTL_KEY='/var/vcap/store/k3s-server/server/tls/etcd/server-client.key' ETCDCTL_API=3 etcdctl endpoint status --cluster --write-out=table
support etcd cli via kine endpoint
In order to support k3s backend change (eg: from mysql to postgres), we need to provide an etcd cli and cli configuration targetting the kine endpoint.
see:
etcdctl: a command line tool for interacting with the etcd server
Support embedded etcd
In order to support k3s backend change (eg: from mysql to embedded etcd), I need to leverage an etcd cli and cli configuration targetting the k3s embedded etcd cluster.
Workaround for missing etcdctl cli on the bosh release
Inspired from https://gist.github.com/superseb/0c06164eef5a097c66e810fe91a9d408 k3s etcd commands
Display nb of keys, from https://etcd.io/blog/2023/how_to_debug_large_db_size_issue/
etcdctl --dial-timeout=20s --command-timeout=50s get /registry --prefix --keys-only | grep -v ^$ | awk -F '/' '{ h[$3]++ } END {for (k in h) print h[k], k}' | sort -nr
The text was updated successfully, but these errors were encountered: