Skip to content

Commit 6adc9e3

Browse files
committed
new post - embedded etcd for k3s
1 parent 821ca8e commit 6adc9e3

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

content/posts/embedded-etcd.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,9 @@ author: "Kapil Agrawal"
66
comments: false
77
---
88

9-
**etcd** is the de-facto KV store for Kubernetes. **k3s** can be run with an embedded etcd as it's KV store which is a great option for running production grade and highly available Kubernetes while keeping overall architecture simple.
9+
[etcd](https://etcd.io) is the de-facto KV store for Kubernetes. [k3s](https://k3s.io) can be run with an embedded etcd as it's KV store which is a great option for running production grade and highly available Kubernetes while keeping overall architecture simple.
1010

11-
There may be situations when you want to interact with it directly in situations like disaster recovery, troubleshooting cluster issues. etcd sync related issues, control leader election, predictability over quorum etc. Accessing the embedded **etcd** is quite trivial although k3s docs do not explain how to do so. All you really need is the `etcdctl` binary.
11+
There may be situations when you want to interact with it directly in situations like disaster recovery, troubleshooting cluster issues. etcd sync related issues, control leader election, predictability over quorum etc. Accessing the embedded etcd is _trivial_ although k3s docs do not explain how to do so. All you really need is the `etcdctl` binary. As I said, it's _trivial_ 😉
1212

1313
Unlike RKE2, k3s does not provide with `etcdctl` client binary during installation so it needs to be installed separately. Below is a simple shell script which downloads the `etcdctl` binary.
1414

0 commit comments

Comments
 (0)