Overview of the Issue In an environment without machines connected to the Internet only via a squid proxy, I have been trying to set up auto_config for my consul clients. However, when I try to switch the oidc_discovery_url from http://vault-server:8200 to https://vault-server:8200, the consul serve...

I automatically attempt to track the latest label of consul and I had a PR today that downgrades my consul releases from 1.14.3 which was marked as latest until yesterday, to 1.12.9 However, since1.12.9 was released, 1.14.4 has been released, which is, I believe, the real latest release Is there a r...

Overview of the Issue When multiple instances of external services are registered with node.address as the DNS name, only the service instance from the first node gets populated in the terminating gateway clusters. Reproduction Steps Steps to reproduce this issue, eg: Run a consul dev cluster $ co...

I`am using Kong 3.1 as Ingress Gateway with Consul 1.14.2 ... Kong is trying to cache service names from K8s DNS like app.default.svc but its not working receiving DNS resolution failed: dns server error. This causing an error on proxy pass before request make. Inside the container I can request the...

Hey, Im trying to create service that includes weight , but eventually traffic is being spitted equally between my services . 2 servers are configured that way: passing: 10000 warning: 10000 1 server configured that way: passing: 1 warning: 1 the service I’m trying to use it is proxy server if that...

Overview of the Issue Hi. Some of our services are stored in /etc/consul/conf.d/ and they are registered by consul agent. The consul agent config includes default and agent tokens. ACL is enabled in our cluster. When upgrading from 1.9.5 to 1.14.3, we noticed that these services are not registered a...

Overview of the Issue After updating our consul server cluster from 1.9.5 to 1.14.3, we found some confusing behavior in the Connect and cert-manager bundle. The following messages began to appear in the logs: Jan 12 13:08:02 consul-primary1 consul[1480197]: 2023-01-12T13:08:02.338+0300 [TRACE] agen...

TODO We should document that consul-k8s 1.0.x and above requires gRPC port to be enabled in the release notes. From consul-k8s issue (#1826) Hi, I run consul-k8s on kubernetes cluster with external (outside of kubernetes) consul servers - just to provide simple k8s services discoverability with cons...

Please search the existing issues for relevant feature requests, and use the reaction feature (https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to add upvotes to pre-existing requests. Feature Description Remove the limit of only 64 operations per transaction U...

Feature Description I am running consul connect in k8s and I want to configure a static cluster in the sidecar that points to a telemetry collector running as a daemonset on each node. Consul knows the node name + ip but there is no way to get them into the static cluster definition, at least based...