search

joatmon08 / consul-k8s-ingress-controllers

Testing for different API gateways with Consul
5 stars 1 forks source link

Multiple Consul services registered from Kong's pod #1

Open minfeng-chan opened 1 year ago

minfeng-chan commented 1 year ago

Hello,

I've received this error whenever i perform the helm install for kong. This is the error logs from the consul injector, how do it fix this?

There are multiple Consul services registered for this pod when there must only be one. Check if there are multiple Kubernetes services selecting this pod and add the label consul.hashicorp.com/service-ignore: "true" to all services except the one used by Consul for handling requests.

pdomineaux commented 1 year ago

Hi,

I can reproduce the issue. It is related to the service account in the helm chart.

The configuration

ingressController: serviceAccount: name: my-service-account

does not exist in recent version of the helm chart.

If I set this:

deployment: serviceAccount: name: external-kong-proxy

It is applied but not working.

Does anyone has a workaround.