discovery.etcd.io | etcd discovery service | Key Value Database library

by coreos Go Version: v2 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(4)Vulnerabilities Install Support

kandi X-RAY | discovery.etcd.io Summary

discovery.etcd.io is a Go library typically used in Database, Key Value Database, Docker applications. discovery.etcd.io has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

If you are having issues with discovery.etcd.io please file a ticket here:

Support

Quality

Security

License

Reuse

Support

discovery.etcd.io has a low active ecosystem.

It has 158 star(s) with 56 fork(s). There are 27 watchers for this library.

It had no major release in the last 12 months.

There are 1 open issues and 25 have been closed. On average issues are closed in 408 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of discovery.etcd.io is v2

Quality

discovery.etcd.io has 0 bugs and 0 code smells.

Security

discovery.etcd.io has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

discovery.etcd.io code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

discovery.etcd.io is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

discovery.etcd.io releases are available to install and integrate.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of discovery.etcd.io

Get all kandi verified functions for this library.

discovery.etcd.io Key Features

No Key Features are available at this moment for discovery.etcd.io.

discovery.etcd.io Examples and Code Snippets

No Code Snippets are available at this moment for discovery.etcd.io.

Community Discussions

Trending Discussions on discovery.etcd.io

CoreOS Cluster with Vagrant does not start/configure etcd correctly

Kubernetes High-Availability Masters

CoreOS v.1.6.1 not starting

hyperkube doesn't start any manifest from /etc/kubernetes/manifests

QUESTION

CoreOS Cluster with Vagrant does not start/configure etcd correctly

Asked 2018-Apr-04 at 11:27

My ultimate goal is to run Kubernetes on a 3-node CoreOS cluster (if anyone has better suggestions, I'm all ears: at this stage, I'm considering CoreOS a complete waste of my time).

I've started following the CoreOS guide to run a Vagrant cluster (I even have the CoreOs in Action book and that's not much help either) - I have obtained a fresh discovery token and modified the user-data and config.rb files as described there:

...

ANSWER

Answered 2018-Apr-04 at 11:27

Unfortunately, the documentation you used is currently outdated. Right now ETCD version 3 is used as a Kubernetes data storage. It provisions with Ignition (VirtualBox Provider (default)):

When using the VirtualBox provider for Vagrant (the default), Ignition is used to provision the machine.

1. Install vagrant-ignition plugin (just in case if this plugin isn't automatically installed when using the default Vagrantfile from coreos-vagrant repo):

Source https://stackoverflow.com/questions/49605297

QUESTION

Kubernetes High-Availability Masters

Asked 2017-Nov-03 at 17:06

I have 2 clusters running in Azure for 2 different Availability Zones and I would like to cluster the etcd masters following https://kubernetes.io/docs/admin/high-availability/#replicated-api-servers .

I created the discovery token for 3 masters. When I try to init etcd container it fails:

...

ANSWER

Answered 2017-Nov-03 at 17:06

Highly Available setups for Kubernetes masters assume you are running multiple (usually 3 so you can have a voting quorum) masters within the same cluster. Your current setup consists of 2 separate 1-master clusters.

When you have multiple clusters, you'll want to look at Cluster Federation although I'd wager this is not what you want, as you'd generally have federated clusters having 3 master setups each as well.

If you can't afford to destroy your existing clusters and boot them up already in HA mode, I suggest this excellent guide for migrating from single to multiple master setups as well as considering using kops for this type of operations.

Source https://stackoverflow.com/questions/47100846

QUESTION

CoreOS v.1.6.1 not starting

Asked 2017-May-21 at 05:48

I am working on setting up a new Kubernetes cluster using the CoreOS documentation. This one uses the CoreOS v1.6.1 image. I am following this documentation from link CoreOS Master setup. I looked in the journalctl logs and I see that the kubeapi-server seems to exit and restart.

The following is a journalctl log indicating on the kube-apiserver :

checking backoff for container "kube-apiserver" in pod "kube-apiserver-10.138.192.31_kube-system(16c7e04edcd7e775efadd4bdcb1940c4)"

Back-off 5m0s restarting failed container=kube-apiserver pod=kube-apiserver-10.138.192.31_kube-system(16c7e04edcd7e775efadd4bdcb1940c4)

Error syncing pod 16c7e04edcd7e775efadd4bdcb1940c4 ("kube-apiserver-10.138.192.31_kube-system(16c7e04edcd7e775efadd4bdcb1940c4)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "Back-off 5m0s restarting failed container=kube-apiserver pod=kube-apiserver-10.138.192.31_kube-system(16c7e04edcd7e775efadd4bdcb1940c4)"

I am wondering if it's because I need to start the new etcd3 version instead of the etcd2? Any hints or suggestion is appreciated.

The following is my cloud-config:

...

ANSWER

Answered 2017-May-16 at 09:40

You use etcd2, so you need to pass the flag '--storage-backend=etcd2' to your kube-apiserver in your manifest.

Source https://stackoverflow.com/questions/43965795

QUESTION

hyperkube doesn't start any manifest from /etc/kubernetes/manifests

Asked 2017-Mar-04 at 15:05

I have Container Linux by CoreOS alpha (1325.1.0) Installed on a pc at home.

I played with kubernetes for a couple of month, but now after reinstalling ContainerOS and trying to install kubernetes using my fork at https://github.com/kfirufk/coreos-kubernetes I fail to properly install kubernetes.

I use hyperkube image v1.6.0-beta.0_coreos.0.

the problem is that it seems that hyperkube doesn't try to initiate any manifests from /etc/kubernetes/manifests. I configured kubelet to run with rkt.

when I run journalctl -xef -u kubelet after restarting kubelet, I get the following output:

...

ANSWER

Answered 2017-Mar-04 at 15:05

thanks to @AntoineCotten the problem was easily resolved.

first, I downgraded hyperkube from v1.6.0-beta.0_coreos.0 to v1.5.3_coreos.0. then I noticed an error in the kubelet log that made me understand that I had a major typo in /opt/bin/host-rkt.

I had exec nsenter -m -u -i -n -p -t 1 -- /usr/bin/rkt "\$@" instead of exec nsenter -m -u -i -n -p -t 1 -- /usr/bin/rkt "$@".

I escaped the $ when trying to paste the command line arguments, which then.. didn't. so.. not using 1.6.0-beta0 for now, that's ok! and fixed the script. now everything works again. thanks

Source https://stackoverflow.com/questions/42473930

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install discovery.etcd.io

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: