search

rancher-sandbox / rancher-desktop

Container Management and Kubernetes on the Desktop
https://rancherdesktop.io
Apache License 2.0
6.05k stars 286 forks source link

Several red warnings in Lens #1599

Open fmunteanu opened 2 years ago

fmunteanu commented 2 years ago

Actual Behavior

I tried Rancher Desktop, there are several red warnings in Lens, which I don't get when I spin a basic EKS cluster. Cluster metrics are not available, ports already in use, invalid dates.

Steps to Reproduce

Install Rancher Desktop and Lens: brew install --cask lens brew install --cask rancher

Open the new running k8s cluster in Lens.

$ kubectl config view
apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: DATA+OMITTED
    server: https://127.0.0.1:6443/
  name: rancher-desktop
contexts:
- context:
    cluster: rancher-desktop
    user: rancher-desktop
  name: rancher-desktop
current-context: rancher-desktop
kind: Config
preferences: {}
users:
- name: rancher-desktop
  user:
    client-certificate-data: REDACTED
    client-key-data: REDACTED

$ kubectl cluster-info
Kubernetes control plane is running at https://127.0.0.1:6443/
CoreDNS is running at https://127.0.0.1:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
Metrics-server is running at https://127.0.0.1:6443/api/v1/namespaces/kube-system/services/https:metrics-server:https/proxy

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.

Result

Screenshots were taken with Rancher Desktop 1.0.0 but same behaviour is present in 1.0.1.

image1 image2 image3

Expected Behavior

I should not have any kind of error.

Additional Information

No response

Rancher Desktop Version

1.0.1

Rancher Desktop K8s Version

1.23.3

Which container runtime are you using?

containerd (nerdctl)

What operating system are you using?

macOS

Operating System / Build Version

macOS Monterey 12.2.1

What CPU architecture are you using?

x64

Linux only: what package format did you use to install Rancher Desktop?

No response

Windows User Only

No response

adamkpickering commented 2 years ago

The first thing I'd do is to take Lens out of the picture and see if things are working from a plain old terminal. I'm curious to see the output of the following commands (from a plain terminal):

kubectl get service -A curl http://localhost:<traefik_http_port>/ curl https://localhost:<traefik_https_port>/

You could also try to find out what is already using those ports. I'm not sure whether the problem would be in the VM or on your host machine, though I'd lean towards your host machine. Something like ss -tlpn or netstat -tlpn should help.

Looking forward to hearing more.