Todd Cooper

/usr/bin/docker` exec -i eksa_1733493551451751668 kubectl get --ignore-not-found -o json --kubeconfig kn01/generated/kn01.kind.kubeconfig Cluster.v1alpha1.anywhere.eks.amazonaws.com --namespace default kn01 { "apiVersion": "anywhere.eks.amazonaws.com/v1alpha1", "kind": "Cluster", "metadata": { "annotations": { "anywhere.eks.amazonaws.com/managed-by-cli": "true", "anywhere.eks.amazonaws.com/management-components-version": "v0.21.1" }, "creationTimestamp":...

I have not kubeconfig. I am relying on eks anywhere to write one. Maybe tht was a first mistake? I am a noob with kubernetes and was hoping that the...

pre-creating the directory did not work :-( .. I will try to figur eout the kubeconfig

I tried the following kubeconfig file which did not work There are no errors on the spun-up VMware machine kn01-etcd-9b7dp I cannot figure out what ip number it's onto log...

I just do not know how to get the ip numbers which I assume you get from eksctl or kubectl I have a DHCP server on my network

I am a noob with VMware also .. I am fairly sure it's getting an IP number just cannot figure it out

I figured that out and I am on the machine which has an IP number 10.0.0.101

What can I look at on the bottle rocket OS for etcd? Is there a log file somewhere? BTW, thanks for all the help

I followed the page the b est I could. I get no logs from using the kubectl line mcooper@ubuntu-server-2404:~$ kubectl -n etcdadm-bootstrap-provider-system logs etcdadm-bootstrap-provider-controller-8hc97 --kubeconfig kubeconfig.yaml Please enter Username: Administrator...

It looks like the etcd is starting OK in its log. the journal has no errors in it. Dec 10 18:44:57 kn01-etcd-z5hbt host-containers@kubeadm-bootstrap[1849]: Waiting for etcd static pods Dec 10...