Deployed a consul connect helm chart with gossip encryption, tls and acls.
successfully deployed and validated with tests from your tutorial @ https://learn.hashicorp.com/tutorials/consul/kubernetes-secure-agents?in=consul/kubernetes
I see errors in the envoy sidecar logs of workload pod:
2020-12-09T19:36:16.140Z [ERROR] agent.anti_entropy: failed to sync remote state: error=“rpc error making call: rpc error making call: failed inserting node: Error while renaming Node ID: “6d177fd3-8f12-716b-656a-c24da9a1f53f”: Node name ae145663-89d4-4dfe-b5b3-b3da3c2ff316 is reserved by node 6e7be530-78ee-4663-4870-b1c5c25659f0 with name ae145663-89d4-4dfe-b5b3-b3da3c2ff316 (10.115.3.5)”
2020-12-09T19:36:22.243Z [ERROR] agent.http: Request error: method=PUT url=/v1/agent/check/register from=10.114.25.4:40684 error=“ServiceID “util-sidecar-5f98688568-rz2h2-util” does not exist”
2020-12-09T19:34:22.127Z [ERROR] agent.http: Request error: method=PUT url=/v1/agent/check/register from=10.114.25.4:43452 error=“ServiceID “util-sidecar-5f98688568-ch4p7-util” does not exist”
2020-12-09T19:34:38.702Z [WARN] agent: grpc: Server.Serve failed to complete security handshake from “10.114.46.2:47230”: tls: first record does not look like a TLS handshake
2020-12-09T19:34:56.774Z [WARN] agent: grpc: Server.Serve failed to complete security handshake from “10.114.46.2:47266”: tls: first record does not look like a TLS handshake
2020-12-09T19:35:22.229Z [ERROR] agent.http: Request error: method=PUT url=/v1/agent/check/register from=10.114.25.4:43692 error=“ServiceID “util-sidecar-5f98688568-ch4p7-util” does not exist”
2020-12-09T19:35:25.917Z [WARN] agent: grpc: Server.Serve failed to complete security handshake from “10.114.46.2:47332”: tls: first record does not look like a TLS handshake
The UI shows all the services as healthy.
Whats the impact of the errors?