New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Consul data plane is replacing consul client agent running in the cluster. How to hit consul HTTP API ? Documentation seems to be outdated #3503

Open

MageshSrinivasulu opened this issue Jan 23, 2024 · 0 comments

Labels

MageshSrinivasulu commented Jan 23, 2024 •

edited

Loading

With the introduction of the consul data plane, the consul client daemon set is getting removed in the Kubernetes.

The documentation seems to be outdated for hitting the consul HTTP API https://developer.hashicorp.com/consul/docs/k8s/installation/install#accessing-the-consul-http-api

Pods cannot reach the consul HTTP API with **${HOST_IP}:8500** since the client agent is not running in the node any more

Do you know if we need to hit the consul server endpoint directly in the future? consul-server.consul.svc.cluster.local:8500

The text was updated successfully, but these errors were encountered:

MageshSrinivasulu added the type/question label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment