<p>I am creating an <code>EKS-Anywhere</code> local cluster by following these steps: <a href="https://anywhere.eks.amazonaws.com/docs/getting-started/local-environment/" rel="nofollow noreferrer">Create local cluster | EKS Anywhere</a></p>
<p>Getting the following error after executing this command.</p>
<p><code>eksctl anywhere create cluster -f $CLUSTER_NAME.yaml</code></p>
<pre><code>Performing setup and validations
Warning: The docker infrastructure provider is meant for local development and testing only
✅ Docker Provider setup is valid
Creating new bootstrap cluster
Installing cluster-api providers on bootstrap cluster
Provider specific setup
Creating new workload cluster
Installing networking on workload cluster
Installing storage class on workload cluster
Installing cluster-api providers on workload cluster
Moving cluster management from bootstrap to workload cluster
Error: failed to create cluster: error moving CAPI management from source to target: failed moving management cluster: Performing move...
Discovering Cluster API objects
Moving Cluster API objects Clusters=1
Creating objects in the target cluster
Deleting objects from the source cluster
Error: action failed after 10 attempts: failed to connect to the management cluster: action failed after 9 attempts: Get https://127.0.0.1:43343/api?timeout=30s: EOF


</code></pre>

falcon
<h1>Upgrade your <code>cert-manager</code></h1>
<p>There is known issue: <a href="https://github.com/kubernetes-sigs/cluster-api/issues/3836" rel="nofollow noreferrer">clusterctl init fails when existing cert-manager runs 1.0+ · Issue #3836 · kubernetes-sigs/cluster-api</a></p>
<p>And there is a solution: <a href="https://github.com/kubernetes-sigs/cluster-api/pull/4013" rel="nofollow noreferrer">⚠️ Upgrade cert-manager to v1.1.0 by fabriziopandini · Pull Request #4013 · kubernetes-sigs/cluster-api</a></p>
<p>And <a href="https://github.com/kubernetes-sigs/cluster-api/issues/3836#issuecomment-836599445" rel="nofollow noreferrer">it works</a>:</p>
<blockquote>
<p>Cluster API is using cert-manager v1.1.0 now, so this should not be a problem anymore</p>
</blockquote>
<p>So, I'd suggest upgrading.</p>
