autok3s icon indicating copy to clipboard operation
autok3s copied to clipboard

Published 20 hours ago • verified publisher icon cnrancher

[BUG] Cluster reports as offline always with k3d

Open KyleSanderson opened this issue 2 years ago • 3 comments

Describe the bug Unable to kube-explore or anything with autok3s. There doesn't seem to be any way to resolve this. 3 masters, 1 worker. 1 master and no workers also throws an error.

To reproduce Steps to reproduce the behavior:

  1. Create a cluster
  2. Refresh the page
  3. Cluster is reported as offline - containers and everything work.

Expected behavior The webpage works.

Screenshots If applicable, add screenshots to help explain your problem.

Environments (please complete the following information):

  • OS: Unraid
  • AutoK3s Version: latest.

Additional context Add any other context about the problem here.

KyleSanderson avatar May 05 '22 04:05 KyleSanderson

@KyleSanderson Thanks for your issue! Could you please provide more information about the issue?

  1. Which command are you using to start AutoK3s server? Are you running AutoK3s with the docker or using binary?
  2. Could you provide your K3d provider configuration about this issue? no matter UI screenshot or CLI command?

JacieChao avatar May 05 '22 08:05 JacieChao

@KyleSanderson Thanks for your issue! Could you please provide more information about the issue?

  1. Which command are you using to start AutoK3s server? Are you running AutoK3s with the docker or using binary?
  2. Could you provide your K3d provider configuration about this issue? no matter UI screenshot or CLI command?

Are you able to provide evidence this works? no matter the configuration attempted it fails with k3d.

KyleSanderson avatar May 05 '22 23:05 KyleSanderson

Are you able to provide evidence this works? no matter the configuration attempted it fails with k3d.

I can create cluster using K3d provider using the following command

autok3s create --provider k3d --master 1 --worker 1 --api-port 0.0.0.0:0 --image rancher/k3s:v1.21.7-k3s1

The cluster works fine and I can also enable kube-explorer from UI and access to kube-explorer dashborad image

I think it would be more helpful if you could provide some reproduce steps and error logs when running AutoK3s.

JacieChao avatar May 07 '22 02:05 JacieChao

Going to close this issue because it is not active for long. Feel free to reopen this issue if there are more informations.

orangedeng avatar Aug 29 '22 06:08 orangedeng