You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Removing service:write from default token is causing errors on consul connect envoy, although a separate token with service:write is specified for the command.
Reproduction Steps
Start with a default token with write permissions for everything.
Start consul connect envoy -sidecar-for=service or consul connect envoy -gateway=ingress with an ACL token with the following policy:
Overview of the Issue
Removing
service:write
fromdefault
token is causing errors onconsul connect envoy
, although a separate token withservice:write
is specified for the command.Reproduction Steps
default
token with write permissions for everything.consul connect envoy -sidecar-for=service
orconsul connect envoy -gateway=ingress
with an ACL token with the following policy:default
token:default
token is being used instead of the token specified for the envoy proxy.Consul info for both Client and Server
Client info
We run a custom fork of consul that has additional logging and adjusts some timeouts, no behavioral changes related to ACLs:
Server info
Operating system and Environment details
x86 debian 12, gcp
Log Fragments
Instance running
consul connect envoy -sidecar-for=service-one
:Instance running
consul connect envoy -gateway=ingress
The text was updated successfully, but these errors were encountered: