vault-cluster | Ansible vault cluster Deploy
kandi X-RAY | vault-cluster Summary
kandi X-RAY | vault-cluster Summary
Ansible vault cluster Deploy
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of vault-cluster
vault-cluster Key Features
vault-cluster Examples and Code Snippets
Community Discussions
Trending Discussions on vault-cluster
QUESTION
I am following this tutorial but I don't know why I am getting these permissions errors when I run some vault commands
...ANSWER
Answered 2021-Nov-08 at 12:28You must use quotes around the token when exporting it:
QUESTION
I am trying to explore vault enterprise but getting permission denied for sidecar when I use the vault enterprise but seems to work fine when I tried to use local vault server.
Here is the repository that contains a working example with the local vault vault-sidecar-injector-app
Vault config
...ANSWER
Answered 2021-Nov-04 at 12:40When you have set the Kubernetes auth into the vault you have used the
QUESTION
I have two kubernetes clusters running on Azure AKS.
- One cluster named APP-Cluster which is hosting application pods.
- One cluster named Vault-Cluster which the Hashicorp Vault is installed on.
I have installed Hashicorp Vault with Consul in HA mode according to below official document. The installation is successful.
https://learn.hashicorp.com/tutorials/vault/kubernetes-minikube?in=vault/kubernetes
But I am quite lost on how to connect and retrieve the secrets in Vault cluster from another cluster. I would like to use the sidecar injection method of Vault for my app cluster to communicate with vault cluster. I tried the follow the steps in below official document but in the document minikube is used instead of public cloud Kubernetes Service. How do I define the "EXTERNAL_VAULT_ADDR" variable for AKS like described in the document for minikube? Is it the api server DNS address which I can get from Azure portal?
https://learn.hashicorp.com/tutorials/vault/kubernetes-external-vault?in=vault/kubernetes
...ANSWER
Answered 2021-Jun-22 at 13:19The way you interact with Vault
is via HTTP(s) API. That means you need to expose the vault
service running in your Vault-Cluster
cluster using one of the usual methods.
As an example you could:
- use a service of type
LoadBalancer
(this works because you are running kubernetes in a cloud provider that supports this feature); - install an ingress controller, expose it (again with a load balancer) and define an
Ingress
resource for yourvault
service. - use a node port service
The EXTERNAL_VAULT_ADDR
value depends on which strategy you want to use.
QUESTION
I am getting continuous TLS handshake errors every 5 sec due to my load balancer pinging vault nodes in every 5 seconds. Kube load balancer is pinging my vault nodes using
nc -vz podip podPort
every 5 sec
I have already disabled client cert verification in my config.hcl but still see below logs in my kubectl logs for vault
...ANSWER
Answered 2020-Sep-04 at 05:51The messages are not about client certs or CA certs, a TLS handshake happens whether the client presents a certificate or not.
Instead, it is because a TCP connection is created and established and the Go library now wants to start a TLS handshake. Instead, the other side (the health checker) just hangs up and the TLS handshake never happens. Go then logs this message.
You are correct in saying that it is harmless, this is purely a side effect of port-liveness health checking. It is however spammy and annoying.
You have two basic options to get around this:
- filter the messages out of the logs when persisting them
- change to a different type of health check
I would recommend the second option: switch to a different health check. Vault has a /sys/health endpoint that can be used with HTTPS health checks.
In addition to getting rid of the TLS warning messages, the health endpoint also allows to you check for active and unsealed nodes.
QUESTION
I have created a vault cluster that uses OpenSSL self-signed certs generated by terraform-aws-vault module
I am getting following error when I tried to create an issuer resource in Kubernetes which uses this Vault cluster.
...ANSWER
Answered 2020-Apr-22 at 14:47That seems to be due to the expected format in yaml file for attribute caBundle. I couldn't find a documented schema for it. But, I found an example https://github.com/kubernetes/kubernetes/issues/61171. The caBundle seems to be taking a single line of string which is base64. I have tested this and it works for me.
It should work if you place entire base64 encoded file in one line and put it against caBundle. Refer to the link posted for an example.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install vault-cluster
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page