Consul-helm: keyring api is not working with server.exposeGossipAndRPCPorts and client.exposeGossipAndPorts

[soonoo]

Reproduction Steps

I installed consul chart with the following values.yml.

global:
  gossipEncryption:
    secretName: consul-gossip-encryption-key
    secretKey: key

server:
  exposeGossipAndRPCPorts: true
  bootstrapExpect: 3
  annotations: |
      "consul.hashicorp.com/service-meta-domain": "http://my-domain.com"
      "consul.hashicorp.com/service-name": "my-consul"
    ports:
        serflan:
            port: 8301
client:
   exposeGossipAndPorts: true

syncCatalog:
    enabled: true
    toConsul: true
    toK8S: true 
    addK8SNamespaceSuffix: false

keyring api faile then.

$ curl http://my-domain.com/v1/operator/keyring
1 error occurred:
    * dc-name (LAN) error: 0/1 nodes reported success

It works with local-only=true parameter.

$ curl http://my-domain.com/v1/operator/keyring?local-only=true
[{"WAN":false,"Datacenter":"groot-k8s","Segment":"","Keys":{"1asdaasdasdasdasdoKsQNIXE=":15},"PrimaryKeys":{"1asdaasdasdasdasdoKsQNIXE=":15},"NumNodes":15}]

Logs

There is nothing special in error log, it simply says that error occured.

Environment details

• consul-k8s version: latest
• consul-helm version: latest

[lkysow]

Hi, this will be fixed in the next release. Until the release you could use the helm chart from master.

[soonoo]

Thank you @lkysow
Can you tell me when the next release date is?

[lkysow]

Sorry we don't yet have clarity on that. Typically we release once every ~6 weeks but that depends on other factors as well.

[soonoo]

Hi @lkysow. Thank you for fixing issue.
After installing the latest release of consul-helm, I'm still getting error.

$ http://abc.com/v1/operator/keyring
2 errors occurred:
    * WAN error: 2/3 nodes reported success
    * k8s (LAN) error: 14/15 nodes reported success

Consul servers print out below warning messages. If you have any idea about what I missed, would you let me know?

2021-03-25T10:04:47.541Z [WARN] agent.server.memberlist.lan: memberlist: Was able to connect to kube-dev-worker-12 but other probes failed, network may be misconfigured
2021-03-25T10:04:48.541Z [WARN] agent.server.memberlist.lan: memberlist: Was able to connect to kube-dev-worker-8 but other probes failed, network may be misconfigured
2021-03-25T10:04:49.541Z [WARN] agent.server.memberlist.lan: memberlist: Was able to connect to kube-dev-worker-10 but other probes failed, network may be misconfigured
2021-03-25T10:04:50.109Z [WARN] agent.server.memberlist.wan: memberlist: Was able to connect to consul-server-1.k8s but other probes failed, network may be misconfigured
2021-03-25T10:04:50.542Z [WARN] agent.server.memberlist.lan: memberlist: Was able to connect to kube-dev-worker-5 but other probes failed, network may be misconfigured
2021-03-25T10:04:51.542Z [WARN] agent.server.memberlist.lan: memberlist: Was able to connect to kube-dev-worker-3 but other probes failed, network may be misconfigured
2021-03-25T10:04:52.542Z [WARN] agent.server.memberlist.lan: memberlist: Was able to connect to consul-server-2 but other probes failed, network may be misconfigured
2021-03-25T10:04:53.543Z [WARN] agent.server.memberlist.lan: memberlist: Was able to connect to kube-dev-worker-1 but other probes failed, network may be misconfigured
2021-03-25T10:04:54.543Z [WARN] agent.server.memberlist.lan: memberlist: Was able to connect to kube-dev-worker-4 but other probes failed, network may be misconfigured
2021-03-25T10:04:55.109Z [WARN] agent.server.memberlist.wan: memberlist: Was able to connect to consul-server-2.k8s but other probes failed, network may be misconfigured

[lkysow]

Hi, this is likely because UDP packets aren't allowed in your network.