Questions tagged [etcd]

A highly-available key value store for shared configuration and service discovery

etcd is a distributed key value store that provides a reliable way to store data across a cluster of machines. It’s open-source and available on GitHub. etcd gracefully handles master elections during network partitions and will tolerate machine failure, including the master.

Your applications can read and write data into etcd. A simple use-case is to store database connection details or feature flags in etcd as key value pairs. These values can be watched, allowing your app to reconfigure itself when they change.

Advanced uses take advantage of the consistency guarantees to implement database master elections or do distributed locking across a cluster of workers.

74 questions
13
votes
1 answer

Graceful shutdown of Kubernetes cluster

We have a 4 node Kubernetes cluster, installed using Juju 2.0 and the official canonical Kubernetes charm. The sole purpose of this very local and private installation is development and testing. One of the biggest and documented issues of this…
5
votes
1 answer

Why would using MongoDB in lieu of etcd as a key value store be a good or bad idea?

I'd like to get general thoughts from the community as to why MongoDB for key/value would OR would not be a suitable replacement for etcd or other purpose-built key/value store system (consol, zookeeper, etc).
DefionsCode
  • 230
  • 3
  • 9
3
votes
1 answer

missing '=' etcd when defining service file

I'm struggling while following Kelsey Hightower's "Kubernetes the Hard Way" tutorial. I've gone off script, because I'm trying to bootstrap k8s on a local server. I've got the point where I'm bootstrapping etcd, however, when I'm creating the…
Baron
  • 61
  • 1
  • 5
3
votes
0 answers

etcd cluster setup with chef - determining initial-cluster-state

I am writing chef scripts to setup an etcd cluster. The list of nodes (including their IPs) will be hardcoded in the chef script (as an attribute) and it will pass them to etcd using static bootstrapping with --initial-cluster and…
Heinzi
  • 171
  • 1
  • 6
3
votes
2 answers

etcd2 fails to start on my CoreOS node

I am trying to start etcd2 in my CoreOS node. I have this in my cloud-config: coreos: etcd2: discovery: https://discovery.etcd.io/new?size=1 advertise-client-urls: http://127.0.0.1:2379,http://127.0.0.1:4001 …
Rox
  • 441
  • 1
  • 6
  • 13
3
votes
1 answer

PostgreSQL failover with Kubernetes

I've got master slave replication working with Kubernetes, but would now like to implement failover. I have pods running with the service=postgresql and role=master or role=slave roles. When the master fails, I want to select another master and…
2
votes
1 answer

CoreOS 1353.4.0 - How should I configure Ignition for an etcd cluster member with dynamic discovery?

Using CoreOS 1353.4.0, on DigitalOcean, how should I write an Ignition config for a machine that is to join an etcd cluster with dynamic discovery? I've written the following Ignition config (basically in keeping with this guide), but there seems to…
aknuds1
  • 2,085
  • 3
  • 16
  • 23
2
votes
0 answers

Weighting an etcd instance to have two quorum votes

For obvious reasons, best practice in building clusters that require distributed consensus is to use 3, 5, or another node count that has a tiebreaker in place. Sometimes, however, one has two physical devices and wants to cluster them. One way to…
Charles Duffy
  • 946
  • 2
  • 10
  • 19
2
votes
1 answer

problems configuring etcd2 for TLS

I have at home two CoreOS stable v1122.2.0 machines. both of them are registered at discovery.etcd.io properly. (i see both of them registered at https://ip:2380 when i browse to the discovery url). the first server is 10.79.218.2, and the 2nd is…
ufk
  • 323
  • 3
  • 7
  • 26
2
votes
1 answer

Why doesn't CoreOS start etcd2 automatically, even though my cloud-config says so?

I am running CoreOS beta 991.1.0 on a Google Compute Engine instance, where cloud-config is configured via the user_data metadata variable. My cloud-config looks like this: #cloud-config write_files: - path: "/etc/kubernetes/kube.conf" …
aknuds1
  • 2,085
  • 3
  • 16
  • 23
2
votes
1 answer

Docker container can't communicate with etcd

I created 3 coreos machines at digitalocean using this cloud-config.yml: https://gist.github.com/socketwiz/d6fe23d19180a1ad8b5a where token was replaced with the one I retrieved from: $ curl -w "\n" "https://discovery.etcd.io/new?size=3" Up to this…
Ricky Nelson
  • 121
  • 2
2
votes
1 answer

etcd2 fails on my CoreOS with my very simple setup

I want to setup a 3 nodes cluster running my own discovery service and I am following this simple guide for static discovery. I know my 3 machines IP addresses and here is when I try to start etcd2 on the first machine: etcd2 -name infra0…
Rox
  • 441
  • 1
  • 6
  • 13
2
votes
1 answer

Resizing Digital Ocean Droplets that use CoreOS break the CoreOs Cluster

I'm new to CoreOs and I have been experimenting with it on DigitalOcean. Let me start out by saying, I'm not sure if this is a DigitalOcean issue or CoreOS issue. How to replicate: Spin up 2 CoreOS and link them together to form a cluster…
mbejda
  • 151
  • 5
2
votes
0 answers

Kubernetes on Flatcar Linux will not start up kube API server after a reboot of the master node

Thank you for reading and taking your time to review this problem. I have a problem using my Kubernetes cluster. It is running Flatcar Linux, made by Kinvolk, recently acquired by Microsoft. I have setup the cluster using their Lokomotive (lokoctl)…
jonasclaes
  • 101
  • 7
2
votes
0 answers

Kubernetes V1.19.13 - kubeapi servers not able connecting to different etcd database

I have upgraded Kubernets cluster ( 3 master, 3 etcd servers database) from 1.18 to v1.19.13 and ETCD to 3.4.13. since than API servers are not stable, keep switching different etcd server, because of this cluster is not working properly. these…
sfgroups
  • 193
  • 3
  • 13
1
2 3 4 5