Kubelet complains that it "Could not determine public DNS from AWS metadata."
Opened this issue · 0 comments
namliz commented
docker run \
-v /tmp/data:/cncf/data \
-e NAME=testing18 \
-e CLOUD=aws \
-e COMMAND=deploy \
-e BACKEND=file \
-e AWS_ACCESS_KEY_ID=secret
-e AWS_SECRET_ACCESS_KEY=secret
-e AWS_DEFAULT_REGION=ap-southeast-2
-ti registry.cncf.ci/cncf/cross-cloud/provisioning:ci-stable-v0-2-0 sh
./provision.sh aws-deploy testing18 file
❯ ssh-add test18.pem
Identity added: test18.pem (test18.pem)
❯ ssh -At core@52.63.149.7 ssh core@etcd1.test18.cncf.demo
The authenticity of host '52.63.149.7 (52.63.149.7)' can't be established.
ECDSA key fingerprint is SHA256:1PtXIBYKaFYEtOM72F/VqWyt/F2cT4tE9rhHJqL6Z0U.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '52.63.149.7' (ECDSA) to the list of known hosts.
The authenticity of host 'etcd1.test18.cncf.demo (10.0.10.84)' can't be established.
ECDSA key fingerprint is SHA256:gaj8NziYhiah5EuTHbuSPMzbwZgX+7UPodf35WQWh24.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'etcd1.test18.cncf.demo,10.0.10.84' (ECDSA) to the list of known hosts.
Container Linux by CoreOS stable (1298.5.0)
core@ip-10-0-10-84
❯ journalctl -fu kubelet
ip-10-0-10-84.ap-southeast-2.compute.internal kubelet[1966]: I0818 09:56:53.827240 1966 aws.go:937] Could not determine public DNS from AWS metadata.
Repeats forever. Could be harmless log spam (that was fixed upstream and shouldn't happen on newer versions), not sure.