Answers: <p>Well, it's labeled as <em>hard</em> :-D</p>
  <p>Without knowing more troubleshooting steps that you've already taken, it's hard to know what to suggest for that first item, but the second one is almost certainly that <a href="https://github.com/kelseyhightower/kubernetes-the-hard-way/blame/79a3f79b27bd28f82f071bb877a266c2e62ee506/docs/07-bootstrapping-etcd.md#L71" rel="nofollow noreferrer">its own name</a> is not present in <a href="https://github.com/kelseyhightower/kubernetes-the-hard-way/blame/79a3f79b27bd28f82f071bb877a266c2e62ee506/docs/07-bootstrapping-etcd.md#L85" rel="nofollow noreferrer">the <code>--initial-cluster</code> list</a>. You'll also want to give etcd the full hostname as AWS's DNS returns it (<code>ip-10-20-30-40.us-east-2.compute.internal</code>), to save yourself future troubles when those etcd members attempt to look up their own name. That's almost certainly true of the <code>Node</code> names if you choose to use <code>cloud-provider=aws</code> when you get to that part, too</p>
  <p>If this is the beginning of your kubernetes journey, then this is a great way to establish your future relationship with <code>etcd</code>, as it will be the source of unending pain and opaque messages. I would actually also encourage you to pause and go through <a href="https://github.com/etcd-io/etcd/tree/v3.4.15/Documentation#getting-started" rel="nofollow noreferrer">their docs</a> because having a very firm grasp on what etcd wants, how to debug it, how to <em>recover from it</em>, and how to drive <code>etcdctl</code> will pay dividends over your future kubernetes lifespan</p>
  
Answers: CC BY-SA 4.0
Answers: 2021-06-17T03:57:47.340Z
Answers: 2021-06-17T03:57:47.340Z
Answers: mdaniel
Answers: <p>There was a mismatch in the --initial-cluster list and the local name i was providing. Be sure to check the configuration carefully when following the tutorial.</p>
  
Answers: CC BY-SA 4.0
Answers: 2024-02-03T21:00:35.200Z
Answers: How did you recover from this? I ran into the same issue, but don't know how to pick myself back up
Answers: Ethel Evans
Answers: CC BY-SA 4.0
Answers: 2021-06-18T18:05:14.450Z
Answers: 2021-06-18T18:05:14.450Z
Answers: Arghya
Body: <p>I followed kelsey Hightower's setting up kubernetes the hard way tutorial <a href="https://github.com/kelseyhightower/kubernetes-the-hard-way" rel="nofollow noreferrer">kubernetes the hard way</a> on AWS</p>
  <p>Stuck on bootstrapping etcd on the first control plane node. There are 2 lines in the error message which concerns me:</p>
  <ol>
  <li>The node is already initialized as member, starting as member..</li>
  </ol>
  <ul>
  <li>i have tried deleting the data directory while reinitializing but still same message</li>
  </ul>
  <ol start="2">
  <li>couldn't find local name in the intial cluster configuration</li>
  </ol>
  <p>Is it picking up old configuration data from somewhere other than the data directory?</p>
  
Tags: <kubernetes><amazon-ec2>
Title: Kubernetes etcd bootstrapping - couldn't find local name <name> in the initial cluster configuration
UserDisplayName: Arghya
ThreadText: # Kubernetes etcd bootstrapping - couldn't find local name <name> in the initial cluster configuration
  
  (Asked by: username_0 on 2021-06-09)
  
  I followed kelsey Hightower's setting up kubernetes the hard way tutorial [kubernetes the hard way](https://github.com/kelseyhightower/kubernetes-the-hard-way) on AWS
  
  Stuck on bootstrapping etcd on the first control plane node. There are 2 lines in the error message which concerns me:
  
  1. The node is already initialized as member, starting as member..
  
  * i have tried deleting the data directory while reinitializing but still same message
  
  2. couldn't find local name in the intial cluster configuration
  
  Is it picking up old configuration data from somewhere other than the data directory?
  
  **Tags:** kubernetes, amazon-ec2
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2021-06-17. Score: 1 | Accepted answer
  
  Well, it's labeled as *hard* :-D
  
  Without knowing more troubleshooting steps that you've already taken, it's hard to know what to suggest for that first item, but the second one is almost certainly that [its own name](https://github.com/kelseyhightower/kubernetes-the-hard-way/blame/79a3f79b27bd28f82f071bb877a266c2e62ee506/docs/07-bootstrapping-etcd.md#L71) is not present in [the `--initial-cluster` list](https://github.com/kelseyhightower/kubernetes-the-hard-way/blame/79a3f79b27bd28f82f071bb877a266c2e62ee506/docs/07-bootstrapping-etcd.md#L85). You'll also want to give etcd the full hostname as AWS's DNS returns it (`ip-10-20-30-40.us-east-2.compute.internal`), to save yourself future troubles when those etcd members attempt to look up their own name. That's almost certainly true of the `Node` names if you choose to use `cloud-provider=aws` when you get to that part, too
  
  If this is the beginning of your kubernetes journey, then this is a great way to establish your future relationship with `etcd`, as it will be the source of unending pain and opaque messages. I would actually also encourage you to pause and go through [their docs](https://github.com/etcd-io/etcd/tree/v3.4.15/Documentation#getting-started) because having a very firm grasp on what etcd wants, how to debug it, how to *recover from it*, and how to drive `etcdctl` will pay dividends over your future kubernetes lifespan
  
  
  ---
  
  ### Answer by username_0 on 2021-06-18. Score: 3
  
  There was a mismatch in the --initial-cluster list and the local name i was providing. Be sure to check the configuration carefully when following the tutorial.
  
  > **Comments:**
  > **username_2**: How did you recover from this? I ran into the same issue, but don't know how to pick myself back up  
  
  ---
  
  