Talos config: context: talos-k8s-aws-tutorialĬa: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUJQakNCOGFBREFnRUNBaEJHVUUyNmNjbGs2d2JSYjhHR0dzZEdNQVVHQXl0bGNEQVFNUTR3REFZRFZRUUsKRXdWMFlXeHZjekFlRncweU1qQTVNRFV4TXpVMU5EbGFGdzB6TWpBNU1ESXhNelUxTkRsYU1CQXhEakFNQmdOVgpCQW9UQlhSaGJHOXpNQ293QlFZREsyVndBeUVBY3ZEZ05SYTlwb01zT2g3SjNFQ3hRMUpyQzFvejEzM2NBRy80CmZhQUJtMU9qWVRCZk1BNEdBMVVkRHdFQi93UUVBd0lDaERBZEJnTlZIU1VFRmpBVUJnZ3JCZ0VGQlFjREFRWUkKS3dZQkJRVUhBd0l3RHdZRFZSMFRBUUgvQkFVd0F3RUIvekFkQmdOVkhRNEVGZ1FVL25acFB3djMrRkd5QUNYRwpNQTZ3UEJqR3B3c3dCUVlESzJWd0EwRUFjaUsrRE0rRUdYcDk2dnpZZU5uM0h1Y2ZwcCtyWkJ5bzNrNHF1VFhkCnNPZGphSWtUV0RJcTFMWTFNMklNUXpHV1lnQzRYSWErQk90MFNkOTQrbjhlQnc9PQotLS0tLUVORCBDRVJUSUZJQ0FURS0tLS0tCg=Ĭrt: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUJNekNCNXFBREFnRUNBaEVBd3I2WG9kMEl6aEJzL1V6bWlYQWNOREFGQmdNclpYQXdFREVPTUF3R0ExVUUKQ2hNRmRHRnNiM013SGhjTk1qSXdPVEExTVRNMU5UUTVXaGNOTXpJd09UQXlNVE0xTlRRNVdqQVRNUkV3RHdZRApWUVFLRXdodmN6cGhaRzFwYmpBcU1BVUdBeXRsY0FNaEFMWFZEV09vd1hCYjVtVC9DR1lLNU40SVAxdzB2RDlUCmZNQUdzNG5QWjhOQW8xSXdVREFPQmdOVkhROEJBZjhFQkFNQ0I0QXdIUVlEVlIwbEJCWXdGQVlJS3dZQkJRVUgKQXdFR0NDc0dBUVVGQndNQ01COEdBMVVkSXdRWU1CYUFGUDUyYVQ4TDkvaFJzZ0FseGpBT3NEd1l4cWNMTUFVRwpBeXRsY0FOQkFCeTRrYWJXd0YxQUk5ZFJCQ08rb3hOOEV2aitPMnJQT0dWTTgySit3OTBjYTE0UisyRTFXVHFVCmE2blljaFFxU0s1NFZuZ0RVTkpjRjI5cVYzTlcyd1E9Ci0tLS0tRU5EIENFUlRJRklDQVRFLS0tLS0K Talos configuration generated with: talosctl gen config talos-k8s-aws-tutorial -with-examples=false -with-docs=false -kubernetes-version 1.22.10 -config-patch '' The connection to the server PUBLIC-IP:6443 was refused (I can get logs for all other services without problems with talosctl logs XXX Environment I can not get etcd logs: talosctl logs etcdĮRROR: rpc error: code = Unknown desc = log "etcd" was not registered It should not be related with security group issues as I have configured it with allow all income and outcome. If I run the verification command I get that it is correct: talosctl validate -config controlplane.yaml -mode cloudĬontrolplane.yaml is valid for cloud mode cluster.allowSchedulingOnControlPlanes: true. Just running talosctl gen config talos-k8s-aws-tutorial -with-examples=false -with-docs=false and then just adding. There should not be anything special in my configuration. : Waiting for service "cri" to be "up", time sync, network, etcd spec (25m44s ago) PUBLIC-IP udevd Running OK 40m39s ago Health check successfulĮVENTS : Waiting for etcd spec (25m43s ago) PUBLIC-IP trustd Running OK 40m33s ago Health check successful PUBLIC-IP machined Running ? 40m41s ago Service started as goroutine PUBLIC-IP kubelet Running OK 40m27s ago Health check successful PUBLIC-IP etcd Waiting ? 34m24s ago Waiting for etcd spec PUBLIC-IP cri Running OK 40m38s ago Health check successful PUBLIC-IP containerd Running OK 40m39s ago Health check successful PUBLIC-IP apid Running OK 40m38s ago Health check successful NODE SERVICE STATE HEALTH LAST CHANGE LAST EVENT After I launch the bootstrap command, etcd is always in WAITING state: # talosctl service I have tried with different options (using LB, using Elastic IP.configure multiple nodes, configure singe node cluster.) and all time I am getting the same error. Hello, I am trying to deploy Talos in AWS as you explain in your documentation
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |