-
Notifications
You must be signed in to change notification settings - Fork 332
API Gateway and Mesh Gateway fails to configure when global name is set. #5046
Copy link
Copy link
Open
Labels
type/bugSomething isn't workingSomething isn't working
Description
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
- Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
- If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Overview of the Issue
When global name is set using helm values (consul in this case).
helm install consul hashicorp/consul \
--values values-ext.yaml \
--set global.name=consul \
--set global.datacenter=dc1 \
--set externalServers.k8sAuthMethodHost=https://$KIND_API_IP:6443 \
--create-namespace --namespace consul --version "1.8.0"The generated ACL roles follow below naming convention.
2025-12-20T22:49:30.522+0530 [ERROR] agent.http: Request error: method=GET url="/v1/acl/role/name/managed-gateway-acl-role?dc=dc1&partition=k8s-wl" from=172.18.0.3:38056 error="Requested role does not exist: ACL not found"
However the available role I could see on UI is
consul-mesh-gateway-acl-role
Reproduction Steps
Consul Server Logs
2025-12-20T22:49:30.522+0530 [ERROR] agent.http: Request error: method=GET url="/v1/acl/role/name/managed-gateway-acl-role?dc=dc1&partition=k8s-wl" from=172.18.0.3:38056 error="Requested role does not exist: ACL not found"
Mesh Gateway container log
2025-12-20T17:42:20.525Z [INFO] Check to ensure a Kubernetes service has been created for this application. If your pod is not starting also check the connect-inject deployment logs.
2025-12-20T17:42:21.529Z [INFO] Unable to find registered gateway; retrying
Logs
output from 'kubectl logs' in relevant components
--->
Expected behavior
Mesh Gateway Container shall succeed but it fails.
Environment details
Kind cluster
Additional Context
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
type/bugSomething isn't workingSomething isn't working