Using the helm charts for Vault and Consul does not register Vault as a service in Consul

Vault
1

Using the following helm chart values successfully creates the pods. Vault also utilizes Consul for storage. It does not register vault as a service with Consul though and I’m still a total newb to this.

Any help would be much appreciated :slight_smile:

consul values:

global:
  datacenter: minidc

# Enable the Consul Web UI via a NodePort
ui:
  service:
    type: 'NodePort'

# Enable Connect for secure communication between nodes
connectInject:
  enabled: true

client:
  enabled: true
  grpc: true

# Use only one Consul server for local development
server:
  replicas: 1
  bootstrapExpect: 1
  disruptionBudget:
    enabled: true
    maxUnavailable: 0
  connect: true

vault values:

server:
  affinity: ""
  ha:
    enabled: true

I tried adding the service_registration below but that causes vault pods to error out

    config: |
      ui = true

      listener "tcp" {
        tls_disable = 1
        address = "[::]:8200"
        cluster_address = "[::]:8201"
      }
      storage "consul" {
        path = "vault"
        address = "HOST_IP:8500"
      }

      service_registration "consul" {
        address      = "HOST_IP:8500"
      }
      service_registration "kubernetes" {}
2

Did you end up figuring out the solution for this? I am having the same issue.