kubernetes pod after upgrade EKS to 1.26

[Awot83]

What happened?

After upgrading EKS cluster to 1.26, the pod of dashboard is in error : Back-off restarting failed container / crashLoopBackoff
the EC2 (compute) is ok,
how can i trouble shoot ?

logs of the pod :
goroutine 1 [running]:
github.com/kubernetes/dashboard/src/app/backend/client/csrf.(*csrfTokenManager).init(0xc00051fae8)
/home/runner/work/dashboard/dashboard/src/app/backend/client/csrf/manager.go:41 +0x30e
github.com/kubernetes/dashboard/src/app/backend/client/csrf.NewCsrfTokenManager(...)
/home/runner/work/dashboard/dashboard/src/app/backend/client/csrf/manager.go:66
github.com/kubernetes/dashboard/src/app/backend/client.(*clientManager).initCSRFKey(0xc000166180)
/home/runner/work/dashboard/dashboard/src/app/backend/client/manager.go:527 +0x94
github.com/kubernetes/dashboard/src/app/backend/client.(*clientManager).init(0x19a62f9?)
/home/runner/work/dashboard/dashboard/src/app/backend/client/manager.go:495 +0x32
github.com/kubernetes/dashboard/src/app/backend/client.NewClientManager(...)
/home/runner/work/dashboard/dashboard/src/app/backend/client/manager.go:594
main.main()
/home/runner/work/dashboard/dashboard/src/app/backend/dashboard.go:96 +0x1cf
2024/11/12 14:53:33 Starting overwatch
2024/11/12 14:53:33 Using namespace: kubernetes-dashboard
2024/11/12 14:53:33 Using in-cluster config to connect to apiserver
2024/11/12 14:53:33 Using secret token for csrf signing
2024/11/12 14:53:33 Initializing csrf token from kubernetes-dashboard-csrf secret
panic: Get "https://XXXXXX/api/v1/namespaces/kubernetes-dashboard/secrets/kubernetes-dashboard-csrf": dial tcp XXXXX: connect: no route to host

What did you expect to happen?

Kubernetes Dashboard is accessible (pod is ok)

How can we reproduce it (as minimally and precisely as possible)?

upgrade cluster control plan from 1.24 to 1.26

Anything else we need to know?

helm.sh/chart=kubernetes-dashboard-6.0.8

What browsers are you seeing the problem on?

No response

Kubernetes Dashboard version

helm.sh/chart=kubernetes-dashboard-6.0.8

Kubernetes version

1.26

Dev environment

No response

[floreks]

Please use the latest released chart.

[Awot83]

hello, i did the upgrade : now i am in v2.7.10
but i have this error

Error while initializing connection to Kubernetes apiserver. This most likely means that the cluster is misconfigured (e.g., it has invalid apiserver certificates or service account's configuration) or the --apiserver-host param points to a server that does not exist. Reason: Get "[https://172.20.0.1:443/version](https://172.20.0.1/version)": dial tcp [172.20.0.1:443](https://172.20.0.1/): connect: no route to host

Refer to our FAQ and wiki pages for more information: https://github.com/kubernetes/dashboard/wiki/FAQ

the cluster is a EKS upgraded to 1.26, what misconfiguration could it be ?

[floreks]

hello, i did the upgrade : now i am in v2.7.10

There is no such version available.

[Awot83]

sorry my mistake : please find the "helm show chart kubernetes-dashboard/kubernetes-dashboard" result :
(it's version: 7.10.0)

apiVersion: v2
dependencies:

• alias: nginx
  condition: nginx.enabled
  name: ingress-nginx
  repository: https://kubernetes.github.io/ingress-nginx
  version: 4.10.1
• condition: cert-manager.enabled
  name: cert-manager
  repository: https://charts.jetstack.io
  version: v1.14.5
• condition: metrics-server.enabled
  name: metrics-server
  repository: https://kubernetes-sigs.github.io/metrics-server/
  version: 3.12.1
• condition: kong.enabled
  name: kong
  repository: https://charts.konghq.com
  version: 2.38.0
  description: General-purpose web UI for Kubernetes clusters
  home: https://github.com/kubernetes/dashboard
  icon: https://raw.githubusercontent.com/kubernetes/kubernetes/master/logo/logo.svg
  keywords:
• kubernetes
• dashboard
  kubeVersion: '>=1.21.0-0'
  maintainers:
• email: [email protected]
  name: desaintmartin
• email: [email protected]
  name: floreks
  name: kubernetes-dashboard
  sources:
• https://github.com/kubernetes/dashboard
  version: 7.10.0