search

cnrancher / autok3s

Run K3s Everywhere
https://www.suse.com
Apache License 2.0
753 stars 76 forks source link

can not deploy kube-explorer when create cluster. #586

Closed jack-liew closed 1 year ago

jack-liew commented 1 year ago

can not deploy kube-explorer with autok3s when create cluster.

  1. choose aliyunoss to download air-gap image.
  2. configure ssh, master and node.
  3. checked kube-explorer.

  4. click [create] cluster, k3s service been deployed to master and node, but The log will prompt somting like "can not deploy Kube-Explorer". kubectl command can also be used.

    • OS: [ubuntu 22.04]
    • Autok3s: [0.70]
JacieChao commented 1 year ago

@jack-liew Could you provide more logs for this issue? Which version of kube-explorer are you using and how to install it?

I tried the following steps and the kube-explorer works as expected.

jack-liew commented 1 year ago

I tried the steps with autok3s web ui:

  • download and execute autok3s binary, then visit http://127.0.0.1:8080
  • modify package-download-source:value = aliyunoss
  • create a airgap package with version v1.27.1+k3s1.
  • configure ssh , and can access 192.168.122.20 normally.
  • checked Enable kube-explorer when creating cluster.
  • create a native cluster on master host: 192.168.122.20.
  • on 192.168.122.20, k3s service is actived , exec kubectl be normal.

but, web page log has an error prompt : time="2023-05-05T21:58:48+08:00" level=error msg="[native] failed to start kube-explorer for cluster dev-single: exec: \"kube-explorer\": executable file not found in $PATH"

time="2023-05-05T21:58:40+08:00" level=info msg="[native] begin to create cluster dev-single..."
time="2023-05-05T21:58:40+08:00" level=info msg="[dev-single] cluster's ssh keys saved"
time="2023-05-05T21:58:40+08:00" level=info msg="[native] executing init k3s cluster logic..."
time="2023-05-05T21:58:40+08:00" level=info msg="[native] creating k3s master-1..."
time="2023-05-05T21:58:40+08:00" level=info msg="the 1/5 time tring to ssh to 192.168.122.20:22 with user root"
mirrors:
docker.io:
endpoint:
- https://fogjl973.mirror.aliyuncs.com
- https://registry-1.docker.io
rewrite: {}
configs: {}
auths: {}
time="2023-05-05T21:58:40+08:00" level=info msg="the 1/5 time tring to ssh to 192.168.122.20:22 with user root"
time="2023-05-05T21:58:42+08:00" level=info msg="[cluster] k3s master command: INSTALL_K3S_EXEC='server --advertise-address=192.168.122.20 --cluster-cidr=10.42.0.0/16 --node-external-ip=192.168.122.20 --tls-san=192.168.122.20 ' INSTALL_K3S_SKIP_DOWNLOAD='true' K3S_TOKEN='6ebfa368601f10348d7174fd599b654a' install.sh"
time="2023-05-05T21:58:42+08:00" level=info msg="the 1/5 time tring to ssh to 192.168.122.20:22 with user root"
[INFO] Skipping k3s download and verify
[INFO] Skipping installation of SELinux RPM
[INFO] Creating /usr/local/bin/kubectl symlink to k3s
[INFO] Creating /usr/local/bin/crictl symlink to k3s
[INFO] Creating /usr/local/bin/ctr symlink to k3s
[INFO] Creating killall script /usr/local/bin/k3s-killall.sh
[INFO] Creating uninstall script /usr/local/bin/k3s-uninstall.sh
[INFO] env: Creating environment file /etc/systemd/system/k3s.service.env
[INFO] systemd: Creating service file /etc/systemd/system/k3s.service
[INFO] systemd: Enabling k3s unit
Created symlink /etc/systemd/system/multi-user.target.wants/k3s.service → /etc/systemd/system/k3s.service.
[INFO] systemd: Starting k3s
time="2023-05-05T21:58:47+08:00" level=info msg="[native] successfully created k3s master-1"
time="2023-05-05T21:58:47+08:00" level=info msg="the 1/5 time tring to ssh to 192.168.122.20:22 with user root"
apiVersion: v1
clusters:
- cluster:
certificate-authority-data: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUJkekNDQVIyZ0F3SUJBZ0lCQURBS0JnZ3Foa2pPUFFRREFqQWpNU0V3SHdZRFZRUUREQmhyTTNNdGMyVnkKZG1WeUxXTmhRREUyT0RNeU9UVXhNalV3SGhjTk1qTXdOVEExTVRNMU9EUTFXaGNOTXpNd05UQXlNVE0xT0RRMQpXakFqTVNFd0h3WURWUVFEREJock0zTXRjMlZ5ZG1WeUxXTmhRREUyT0RNeU9UVXhNalV3V1RBVEJnY3Foa2pPClBRSUJCZ2dxaGtqT1BRTUJCd05DQUFReVRUVEYwbGlmREkzWVM2R3daSk93M3RJbTAzWXZLMmEzcFR0ckVQak0KYWRNZFYycWFqak9NZGF2YjhSRzk2ZFBwTUlrRUV3R29zNXRwdTNPcmhJa21vMEl3UURBT0JnTlZIUThCQWY4RQpCQU1DQXFRd0R3WURWUjBUQVFIL0JBVXdBd0VCL3pBZEJnTlZIUTRFRmdRVXdGemNmQ1pBMGdMWkF6alpXN0VPCkFuekNubmd3Q2dZSUtvWkl6ajBFQXdJRFNBQXdSUUlnQ2o0TXZKcmpBSEcrcElZUXdnUkVSd2JodGtSaXRXMEsKcEs5R2tMWlk5KzRDSVFDbmJOU1NVT2JXS0ZwUFhkd1BGZUpmeVQyMGZ1Y1crRzIrTkU3cjdkMzJCUT09Ci0tLS0tRU5EIENFUlRJRklDQVRFLS0tLS0K
server: https://127.0.0.1:6443
name: default
contexts:
- context:
cluster: default
user: default
name: default
current-context: default
kind: Config
preferences: {}
users:
- name: default
user:
client-certificate-data: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUJrVENDQVRlZ0F3SUJBZ0lJV2dqdzRBajNPdmN3Q2dZSUtvWkl6ajBFQXdJd0l6RWhNQjhHQTFVRUF3d1kKYXpOekxXTnNhV1Z1ZEMxallVQXhOamd6TWprMU1USTFNQjRYRFRJek1EVXdOVEV6TlRnME5Wb1hEVEkwTURVdwpOREV6TlRnME5Wb3dNREVYTUJVR0ExVUVDaE1PYzNsemRHVnRPbTFoYzNSbGNuTXhGVEFUQmdOVkJBTVRESE41CmMzUmxiVHBoWkcxcGJqQlpNQk1HQnlxR1NNNDlBZ0VHQ0NxR1NNNDlBd0VIQTBJQUJHVnJ5MkpVTCtDcXFMVWoKa1h3ZWhERXFWSUR1OThXU1h5cWRENFI2SVZYc3R6bmY1UVlqZTdwaHdWV0N5QWRFdXpRWUwzcUlSZ0RjdXR2dgp5a3ZpU2VDalNEQkdNQTRHQTFVZER3RUIvd1FFQXdJRm9EQVRCZ05WSFNVRUREQUtCZ2dyQmdFRkJRY0RBakFmCkJnTlZIU01FR0RBV2dCVDA2UUFwRHhHcmhPVlNIanpKcEo3aHlxdDdMREFLQmdncWhrak9QUVFEQWdOSUFEQkYKQWlBUC8xWlZsU1FmV3JNd2FLSE91LzQvMVNHRUlsbmpFODFzYlZVejMwWTcrZ0loQU5jTi84SWNCUTkyTjZLTgpqVjc1Z1hLSVp1YlpRTTFsUGdUUGdmb3QzTHFQCi0tLS0tRU5EIENFUlRJRklDQVRFLS0tLS0KLS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUJkekNDQVIyZ0F3SUJBZ0lCQURBS0JnZ3Foa2pPUFFRREFqQWpNU0V3SHdZRFZRUUREQmhyTTNNdFkyeHAKWlc1MExXTmhRREUyT0RNeU9UVXhNalV3SGhjTk1qTXdOVEExTVRNMU9EUTFXaGNOTXpNd05UQXlNVE0xT0RRMQpXakFqTVNFd0h3WURWUVFEREJock0zTXRZMnhwWlc1MExXTmhRREUyT0RNeU9UVXhNalV3V1RBVEJnY3Foa2pPClBRSUJCZ2dxaGtqT1BRTUJCd05DQUFUS0t6SkRBZkVLSDZuODZZNDNXdkthWWlaVFdMVGR2aXVsMFV2Q1FENDIKT1hiVXZNSmZsbG1qWHVSN0RXYlRtZ1pudFl1NEpvc0Jvb0JQVXFzaDU2QWFvMEl3UURBT0JnTlZIUThCQWY4RQpCQU1DQXFRd0R3WURWUjBUQVFIL0JBVXdBd0VCL3pBZEJnTlZIUTRFRmdRVTlPa0FLUThScTRUbFVoNDh5YVNlCjRjcXJleXd3Q2dZSUtvWkl6ajBFQXdJRFNBQXdSUUlnT0Z3cE9uVzUxYnMzM01FRXdnNGdjcjBHSnJkSnhMa0UKQ1VVUTVXYW9vRThDSVFEN3hZU0orL3NwUW5QREVhQk9wd1hhZlQ5M21sbzRQY0FxcTBNRlNHaXlLdz09Ci0tLS0tRU5EIENFUlRJRklDQVRFLS0tLS0K
client-key-data: LS0tLS1CRUdJTiBFQyBQUklWQVRFIEtFWS0tLS0tCk1IY0NBUUVFSUtsUzEvREd5eTUzTGxSUGREYjNHNXdacEVlTjdPWXd4MkpxUC9sQ0xqUXZvQW9HQ0NxR1NNNDkKQXdFSG9VUURRZ0FFWld2TFlsUXY0S3FvdFNPUmZCNkVNU3BVZ083M3haSmZLcDBQaEhvaFZleTNPZC9sQmlONwp1bUhCVllMSUIwUzdOQmd2ZW9oR0FOeTYyKy9LUytKSjRBPT0KLS0tLS1FTkQgRUMgUFJJVkFURSBLRVktLS0tLQo=
time="2023-05-05T21:58:48+08:00" level=info msg="[native] deploying additional manifests"
time="2023-05-05T21:58:48+08:00" level=error msg="[native] failed to start kube-explorer for cluster dev-single: exec: \"kube-explorer\": executable file not found in $PATH"
time="2023-05-05T21:58:48+08:00" level=info msg="[native] successfully deployed additional manifests"
time="2023-05-05T21:58:48+08:00" level=info msg="[native] successfully executed init k3s cluster logic"
time="2023-05-05T21:58:48+08:00" level=info msg="=========================== Prompt Info ==========================="
time="2023-05-05T21:58:48+08:00" level=info msg="Use 'autok3s kubectl config use-context dev-single'"
time="2023-05-05T21:58:48+08:00" level=info msg="Use 'autok3s kubectl get pods -A' get POD status`"
JacieChao commented 1 year ago

@jack-liew The log shows that you don't have the executable kube-explorer on your host. Please check if you have kube-explorer on your host.

If you are using AutoK3s running in docker, the kube-explorer is available in the docker image. If you are using AutoK3s binary, you can try the command below to install both AutoK3s and kube-explorer.

curl -sS https://rancher-mirror.rancher.cn/autok3s/install.sh  | sh
jack-liew commented 1 year ago

kube-explorer

I had a wrong thought that kube-explorer was automatically deployed in the master container by Autok3s.

Now I understood. its a web app.

Thank jacie. [手动狗头]