-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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.
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
agent: Service deregistration blocked by ACLs #19717
Comments
Just want to gather more info to help us reproduce the issue:
|
|
Thanks for the updated info. Consul-k8s should handle deregistering service if you remove the service by However, consul will not deregister the stopped service automatically since the service instance is stored in Consul's catalog. Consul won't route traffic to the failed instance, so the connection from downstream will be directed to healthy instances of the service. Could you provide more details about the situation of |
I have the same problem, and I fixed, service need a agent token to regiester and deregister. |
The token has been configured. Client issues, not supported consul 1.16.2. consul recovers after version degradation. |
@Rabbit-st Degraded to which version? Facing similar issues. Also please reopen this issue |
Overview of the Issue
After upgrading from version 1.14.4 to version 1.16.2, there will be service health detection failures registered on some nodes every once in a while, and they will be restored to normal by restarting the consult server.
Reproduction Steps
I don't know how to reproduce it, but it appears every once in a while.
Consul info for both Client and Server
Client info
Server info
Operating system and Environment details
Deploy using consult k8s
Log Fragments
The text was updated successfully, but these errors were encountered: