Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
K3s cluster creation error
See original GitHub issueHello
I’m currently trying to use kcli to create a K3s cluster with VSphere using the following plan: https://gist.github.com/alexander-bruun/887634f6e1237a4b90912f8de2638e82
When i then execute:
kcli create kube k3s --paramfile $kcliPlanFilePath $clustername
I get the following error:
The error occured after switching to a new Network in the plan. (I also updated the network in .kcli/config)
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
[BUG] Cluster creation fails when specifying k3s image v1 ...
When I attempt to start a cluster with kubernetes 1.19.16, the cluster creation fails with the following series of messages. $ k3d cluster...
Read more >Quickly (and simply) create a k8s cluster with k3s |・∀・
If you tried to run k3s kubectl on an agent, you'll notice that it returns an error about localhost:8080 being refused. This is...
Read more >How to resolve error in k3s installation :Job for k3s.service failed
Your command seems to have two issues: INSTALL_K3S_EXEC=“—write-kubeconfig=/home/ubuntu/.kube/config --write-kubeconfig-mode=644”.
Read more >Advanced Options and Configuration | K3s
This section contains advanced information describing the different ways you can run and manage K3s, as well as steps necessary to prepare the...
Read more >Debug Pods - Kubernetes
This is not a guide for people who want to debug their cluster. ... and that the error was silently ignored when you...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
fixed in https://github.com/karmab/kcli/commit/5a597c7a25689cbf58a4d759b4ae482ba1f9523f the issue was that a reset of an additional attribute, the portKey, was needed when switching the dvs information in the first nic from the template to the target vm
Here is the kcli config that I’m using: https://gist.github.com/alexander-bruun/bdb85b17c33c829a6bbb16f8f43a506c