Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Node registration failure due to reserved node names #107
I am running the latest helm chart 0.5.0 but upgraded the images for consul to latest at the time of this ticket.
I noticed that some of my clients started to throw up this error and lead me to the ticket linked below.
There is no guarantee that a statefulset deployment on EKS will remain on the same node, it is possible that it can change within the same AZ and so the node data in the PVC will now be incorrect. It may be an idea to have this enabled by default within the chart.
In this case, the
Given this, there's not currently a mechanism for the Consul/Kubernetes integration to resolve this without it first being fixed in Consul.
Since the issue is already being actively tracked in the Consul and there is no additional work needed in the Helm chart to support a fix, I'm going to close this. For continued updates, please follow hashicorp/consul#4741.