consul-k8s | First-class support for Consul Service Mesh on Kubernetes | Configuration Management library

by hashicorp Go Version: v1.2.0-rc1 License: MPL-2.0

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

kandi X-RAY | consul-k8s Summary

consul-k8s is a Go library typically used in Devops, Configuration Management, Docker applications. consul-k8s has no bugs, it has no vulnerabilities, it has a Weak Copyleft License and it has low support. You can download it from GitHub.

The consul-k8s-control-plane binary includes first-class integrations between Consul and Kubernetes. The project encapsulates multiple use cases such as syncing services, injecting Connect sidecars, and more. The Kubernetes integrations with Consul are documented directly on the Consul website. This README will present a basic overview of use cases and installing the Helm charts, but for full documentation please reference the Consul website. This project is versioned separately from Consul. Supported Consul versions for each feature will be noted below. By versioning this project separately, we can iterate on Kubernetes integrations more quickly and release new versions without forcing Consul users to do a full Consul upgrade. :warning: Please note: We take Consul's security and our users' trust very seriously. If you believe you have found a security issue in Consul K8s, please responsibly disclose by contacting us at security@hashicorp.com.

Support

Quality

Security

License

Reuse

Support

consul-k8s has a low active ecosystem.

It has 612 star(s) with 282 fork(s). There are 45 watchers for this library.

It had no major release in the last 12 months.

There are 129 open issues and 402 have been closed. On average issues are closed in 170 days. There are 58 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of consul-k8s is v1.2.0-rc1

Quality

consul-k8s has no bugs reported.

Security

consul-k8s has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

consul-k8s is licensed under the MPL-2.0 License. This license is Weak Copyleft.

Weak Copyleft licenses have some restrictions, but you can use them in commercial projects.

Reuse

consul-k8s releases are available to install and integrate.

Installation instructions, 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 consul-k8s

Get all kandi verified functions for this library.

consul-k8s Key Features

No Key Features are available at this moment for consul-k8s.

consul-k8s Examples and Code Snippets

No Code Snippets are available at this moment for consul-k8s.

Community Discussions

Trending Discussions on consul-k8s

Consul syncCatalog on k8s keep falling into CrashLoopBackOff

How to Sync K8s Service to Consul Cluster which is outside the K8s？

QUESTION

Consul syncCatalog on k8s keep falling into CrashLoopBackOff

Asked 2020-Mar-29 at 21:10

I am deploying a consul cluster on k8s version 1.9:

...

ANSWER

Answered 2020-Mar-29 at 20:21

When using k8s ingresses with ClusterIPs the consul address should be set to the ingress host, as it is actually exposed, without the port. That means that the corresponding part of the k8s deployment should be like that:

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

QUESTION

How to Sync K8s Service to Consul Cluster which is outside the K8s？

Asked 2019-May-27 at 02:30

From the consul-k8s document： The Consul server cluster can run either in or out of a Kubernetes cluster. The Consul server cluster does not need to be running on the same machine or same platform as the sync process. The sync process needs to be configured with the address to the Consul cluster as well as any additional access information such as ACL tokens.

The consul cluster I am trying to sync is outside the k8s cluster, based on the document, I must pass the address to consul cluster for sync process.However, the helm chart for installing the sync process didn’t contains any value to configure the consul cluster ip address.

...

ANSWER

Answered 2019-May-27 at 02:30

It looks like the sync service runs via the consul agent on the k8s host.

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

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

Vulnerabilities

No vulnerabilities reported

Install consul-k8s

consul-k8s is distributed in multiple forms:.
The recommended installation method is the official Consul Helm chart. This will automatically configure the Consul and Kubernetes integration to run within an existing Kubernetes cluster.
A Docker image hashicorp/consul-k8s-control-plane is available. This can be used to manually run consul-k8s-control-plane within a scheduled environment.
Consul K8s CLI, distributed as consul-k8s, can be used to install and uninstall Consul Kubernetes. See the Consul K8s CLI Reference for more details on usage.
Raw binaries are available in the HashiCorp releases directory. These can be used to run consul-k8s directly or build custom packages.

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: