You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[BUG] The entrypoint script in an agent node continuously fails at the line until kubectl uncordon "$HOSTNAME"; do sleep 3; done as KUBECONFIG not set
#1420
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
To see the agent logs be fine, instead it's plagued with:
E0328 11:09:48.838205 424 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
E0328 11:09:48.838726 424 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
E0328 11:09:48.840152 424 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
E0328 11:09:48.840786 424 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
The connection to the server localhost:8080 was refused - did you specify the right host or port?
Which version of k3d
k3d version v5.6.0
k3s version v1.21.7-k3s1 (default)
I'm deploying k3s version 1.29.x
The problem is in the entrypoint script for a k3s agent node, at the line:
until kubectl uncordon "$HOSTNAME"; do sleep 3; done
That continuously fails, because $KUBECONFIG is not set, so it defaults to http:/localhost:8080. Not sure if I'm understanding the situation correctly but that seems to be it
The text was updated successfully, but these errors were encountered:
What did you do
k3d cluster create --config "k3d.yaml"
My
k3d.yaml
config:What did you expect to happen
To see the agent logs be fine, instead it's plagued with:
Which version of
k3d
I'm deploying k3s version 1.29.x
The problem is in the entrypoint script for a k3s agent node, at the line:
That continuously fails, because
$KUBECONFIG
is not set, so it defaults tohttp:/localhost:8080
. Not sure if I'm understanding the situation correctly but that seems to be itThe text was updated successfully, but these errors were encountered: