consul - kubernetes | agent: [core]grpc: Server.Serve failed to complete security handshake

Viewed 23

I am creating Consul cluster on Kubernetes with the help of the official Helm Chart. I did enable TLS for the Consul cluster and I am using Vault as the Server TLS Certificate Provider on Kubernetes link.

Everything seems to work (3 server nodes and 3 clients) But I am getting a strange warning in one of the clients and I can really understand why I am seeing it.

here is the warning:

2022-09-09T17:46:26.980Z [WARN]  agent: [core]grpc: Server.Serve failed to complete security handshake from "10.0.43.145:51986": remote error: tls: unknown certificate authority
2022-09-09T17:46:37.157Z [WARN]  agent: [core]grpc: Server.Serve failed to complete security handshake from "10.0.43.145:58314": remote error: tls: unknown certificate authority
2022-09-09T17:47:00.132Z [WARN]  agent: [core]grpc: Server.Serve failed to complete security handshake from "10.0.43.145:44934": remote error: tls: unknown certificate authority
2022-09-09T17:47:02.932Z [WARN]  agent: [core]grpc: Server.Serve failed to complete security handshake from "10.0.43.145:44936": remote error: tls: unknown certificate authority

and here is the consul helm values


global:
  name: consul
  datacenter: consul
  secretsBackend:
    vault:
      enabled: true
      manageSystemACLsRole: consul-server-acl-init
      consulServerRole: consul-server
      consulClientRole: consul-client
      consulCARole: consul-ca

  acls:
    manageSystemACLs: true
    bootstrapToken:
      secretName: consul/data/secret/consul/bootstrap-token
      secretKey: token

  gossipEncryption:
    secretName: consul/data/secret/consul/gossip
    secretKey: key

  tls:
    enableAutoEncrypt: true
    enabled: true
    caCert:
      secretName: "pki/cert/ca"

server:
  serverCert:
    secretName: "pki/issue/consul-server"
  replicas: 3
  bootstrapExpect: 3
  securityContext:
    runAsNonRoot: false
    runAsUser: 0
  storage: 10Gi
  connect: false

client:
  enabled: true

any ideas on how to solve this warning message?

0 Answers
Related