如何解决K3S安装中的错误：K3S.服务的工作失败
我在Ubuntu实例上安装K3并将MySQL AWS RD与主节点连接起来时面临问题。我已经制作了1个主节点和3个Worker节点。当我尝试执行以下以下命令时，我会出现错误。请帮助我。我检查了安全组中的入站和出站规则，该规则附加了RDS和EC2实例，但效果很好。请帮忙！！！
Job for k3s.service failed because the control process exited with error code.
See "systemctl status k3s.service" and "journalctl -xe" for details.
安装命令在用DB名称K3S
export K3S_DATASTORE_ENDPOINT='mysql://k3s:<xxxdbpasswordxxx>@tcp(k3s-cluster-db.cz2c5bol8r6l.us-east-1.rds.amazonaws.com:3306)/k3s'
curl -sfL https://get.k3s.io | INSTALL_K3S_EXEC="--write-kubeconfig=/home/ubuntu/.kube/config --write-kubeconfig-mode=644" sh -
错误：
入站规则
出站规则
systemctl状态k3s.service
journalctl -xe
I am facing problem in installing K3s on Ubuntu instance and connecting mysql AWS RDS with the master node . I have made 1 master node and 3 worker node .When I try to execute the following commands below I get error. Please help me with this .I checked the inbound and outbound rules in security group which is attached to RDS and EC2 instance but it works fine . Please Help !!!!
Job for k3s.service failed because the control process exited with error code.
See "systemctl status k3s.service" and "journalctl -xe" for details.
INSTALLATION COMMANDS after making RDS mysql dataabse with db name k3s
export K3S_DATASTORE_ENDPOINT='mysql://k3s:<xxxdbpasswordxxx>@tcp(k3s-cluster-db.cz2c5bol8r6l.us-east-1.rds.amazonaws.com:3306)/k3s'
curl -sfL https://get.k3s.io | INSTALL_K3S_EXEC="--write-kubeconfig=/home/ubuntu/.kube/config --write-kubeconfig-mode=644" sh -
ERROR :
INBOUND RULES
OUTBOUND RULES
systemctl status k3s.service
journalctl -xe
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您的命令似乎有两个问题：
“而不是”可能会被外壳误解- write-kubeconfig应该使用<代码> - （如中 - - write-kubeconfig），因为错误消息是
flag提供的，但未定义：-write-kube-config（并且具有-），以上可能只是字体/显示问题。在这种情况下，检查是否是。
Your command seems to have two issues:
“instead of"can be misinterpreted by the shell—write-kubeconfigshould use--(as in—-write-kubeconfig)Since the error message is
flag provided but not defined: --write-kube-config(and has--), it is possible the above is just a font/display issue.In that case, check if this is an option order issue as described here.