Can't see container logs on K8S 1.30

[mdemri]

Describe the bug
Can't see container logs

To Reproduce
Steps to reproduce the behavior:

1. Go to some container
2. Press enter for its logs
3. I dont see the actual logs, but
4. stream logs failed Get "https://10.0.0.21:10250/containerLogs/dex/CONTAINER_NAME-0/app?follow=true&tailLines=100&timestamps=true": proxy error from 127.0.0.1:6443 while dialing 10.0.0.21:10250, code 502: │
   │ 502 Bad Gateway for dex/CONTAINER_NAME-0 (app) │
   │ stream logs failed Get "https://10.0.0.21:10250/containerLogs/dex/CONTAINER_NAME-0/app?follow=true&tailLines=100&timestamps=true": proxy error from 127.0.0.1:6443 while dialing 10.0.0.21:10250, code 502: │
   │ 502 Bad Gateway for dex/CONTAINER_NAME-0 (app) │
   │ stream logs failed Get "https://10.0.0.21:10250/containerLogs/dex/CONTAINER_NAME-0/app?follow=true&tailLines=100&timestamps=true": proxy error from 127.0.0.1:6443 while dialing 10.0.0.21:10250, code 502: │
   │ 502 Bad Gateway for dex/CONTAINER_NAME-0 (app) │
   │ stream logs failed Get "https://10.0.0.21:10250/containerLogs/dex/CONTAINER_NAME-0/app?follow=true&tailLines=100&timestamps=true": proxy error from 127.0.0.1:6443 while dialing 10.0.0.21:10250, code 502: │
   │ 502 Bad Gateway for dex/CONTAINER_NAME-0 (app) │
   │ stream logs failed Get "https://10.0.0.21:10250/containerLogs/dex/CONTAINER_NAME-0/app?follow=true&tailLines=100&timestamps=true": proxy error from 127.0.0.1:6443 while dialing 10.0.0.21:10250, code 502: │
   │ 502 Bad Gateway for dex/CONTAINER_NAME-0 (app) │
   │ stream logs failed Get "https://10.0.0.21:10250/containerLogs/dex/CONTAINER_NAME-0/app?follow=true&tailLines=100&timestamps=true": proxy error from 127.0.0.1:6443 while dialing 10.0.0.21:10250, code 502: │
   │ 502 Bad Gateway for dex/CONTAINER_NAME-0 (app) │
   │ stream logs failed Get "https://10.0.0.21:10250/containerLogs/dex/CONTAINER_NAME-0/app?follow=true&tailLines=100&timestamps=true": proxy error from 127.0.0.1:6443 while dialing 10.0.0.21:10250, code 502:

Historical Documents
When applicable please include any supporting artifacts: k9s debug logs, configurations, resource manifests, ...

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
None

Versions (please complete the following information):

• OS: Mac OS
• K9s: 0.32.5
• K8s: 1.30.3

Additional context
In Kubernetes 1.28 it works well..

[thejoeejoee]

does it show logs when used the context/pod with kubectl logs?