consul-helm | Helm chart to install Consul | Configuration Management library

by hashicorp Shell Version: v0.32.1 License: MPL-2.0

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

kandi X-RAY | consul-helm Summary

consul-helm is a Shell library typically used in Devops, Configuration Management applications. consul-helm 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 Helm chart has been moved to hashicorp/consul-k8s under the charts/consul directory. ️. Please direct all pull requests and issues to that repository.

Support

Quality

Security

License

Reuse

Support

consul-helm has a low active ecosystem.

It has 408 star(s) with 389 fork(s). There are 36 watchers for this library.

It had no major release in the last 12 months.

There are 0 open issues and 366 have been closed. On average issues are closed in 44 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of consul-helm is v0.32.1

Quality

consul-helm has 0 bugs and 0 code smells.

Security

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

consul-helm code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

consul-helm 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-helm releases are available to install and integrate.

It has 4823 lines of code, 116 functions and 54 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

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-helm

Get all kandi verified functions for this library.

consul-helm Key Features

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

consul-helm Examples and Code Snippets

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

Community Discussions

Trending Discussions on consul-helm

how to expose ingress for Consul

apiVersion is not the same as in the helm template

Hashicorp Consul - How to do verified TLS from Pods in Kubernetes cluster

Consul syncCatalog on k8s keep falling into CrashLoopBackOff

Consul on Kubernetes: Consul pods are running but not ready

QUESTION

how to expose ingress for Consul

Asked 2020-Oct-16 at 08:26

I'm trying to add consul ingress to my project, and I'm using this GitHub repo as a doc for ui and ingress: here and as you can see unfortunately there is no ingress in doc, there is an ingressGateways which is not useful because doesn't create ingress inside Kubernetes(it can just expose URL to outside)

I have searched a lot, there are 2 possible options:

1: create extra deployment for ingress

2: create consul helm chart to add ingress deploy

(unfortunately I couldn't find a proper solution for this on the Internet)

...

ANSWER

Answered 2020-Oct-15 at 15:24

The ingressGateways config in the Helm chart is for deploying a Consul ingress gateway (powered by Envoy) for Consul service mesh. This is different from a Kubernetes Ingress.

Consul's ingress enables routing to applications running inside the service mesh, and is configured using an ingress-gateway configuration entry (or in the future using Consul CRDs). It cannot route to endpoints that exist outside the service mesh, such as Consul's API/UI endpoints.

If you need a generic ingress that can route to applications outside the mesh, I recommend using a solution such as Ambassador, Traefik, or Gloo. All three of this also support integrations with Consul for service discovery, or service mesh.

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

QUESTION

apiVersion is not the same as in the helm template

Asked 2020-Sep-26 at 12:57

I'm using consul helm chart repo to install consul agent. I'm installing the chart on my minikube cluster (version 1.10). The template of the daemonSet for consul client shows apiVersion: apps/v1. When i'm installing consul and checking the apiVersion I get a different version:

...

ANSWER

Answered 2020-Sep-26 at 12:57

The Kubernetes API Server version is 1.10.0 and kubectl client version is 1.16. Before Kubernetes API Server version 1.16 DaemonSet were in extensions/v1beta1 which was changed to apps/v1 in Kubernetes API Server version 1.16. You should upgrade Kubernetes API Server version to 1.16 or later if you want to use DaemonSet with apps/v1

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

QUESTION

Hashicorp Consul - How to do verified TLS from Pods in Kubernetes cluster

Asked 2020-May-31 at 00:11

I'm having some difficulty understanding Consul end-to-end TLS. For reference, I'm using Consul in Kubernetes (via the hashicorp/consul Helm chart). Only one datacenter and Kubernetes cluster - no external parties or concerns.

I have configured my override values.yaml file like so:

...

ANSWER

Answered 2020-May-31 at 00:11

Solved with thanks to Hashicorp on their Consul discussion forum.

Create a Kubernetes secret named consul with a key named CONSUL_GOSSIP_ENCRYPTION_KEY and an appropriate encryption key value.
- Generate value using consul keygen
Install the hashicorp/consul Helm chart with an values-override.yaml , such as below:

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

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

Consul on Kubernetes: Consul pods are running but not ready

Asked 2020-Jan-15 at 16:07

I am creating a 3-node cluster inside an Ubuntu VM running on my Mac using Kind. They work as they should:

...

ANSWER

Answered 2020-Jan-15 at 14:04

I replicated your setup creating 3 node cluster (1 master and 2 workers) and deployed consul with helm and saw the same thing as you see. All pods were running beside one that was pending.

In statefulset object you can see there is podAntiAffinity which disallows scheduling 2 or more server pods on the same node. This is why You see one pod in pending state.

There are 4 ways I come up with you can make it work.

Master node has a taint: node-role.kubernetes.io/master:NoSchedule which disallows scheduling any pods on master node. You can delete this taint by running: kubectl taint node kind-control-plane node-role.kubernetes.io/master:NoSchedule- (notice minus sign, it tells k8s to delete the taint) so now scheduler will be able to schedule the one consul-server pod that's left to this node.
You can add one more worker node.
You can remove podAntiAffinity from consul-server statfulset object so scheduler won't care where pods get scheduled.
Change requiredDuringSchedulingIgnoredDuringExecution to preferredDuringSchedulingIgnoredDuringExecution so this affinity rule does not need to be fulfilled, it's only preferred.

Let me know if it helped.

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

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

Vulnerabilities

No vulnerabilities reported

Install consul-helm

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: