Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting --auto-generate-certificates on kubernetes-dashboard-web causes error #9489

Open
Michkov opened this issue Sep 26, 2024 · 1 comment
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@Michkov
Copy link

Michkov commented Sep 26, 2024

What happened?

I have kubernetes-dashboard installation from helm. I have added arg --auto-generate-certificates to deployment. But pod is failing on:

I0926 12:20:55.201494       1 main.go:37] "Starting Kubernetes Dashboard Web" version="1.4.0"
I0926 12:20:55.202208       1 init.go:47] Using in-cluster config
2024/09/26 12:20:55 Successfully created certificates
2024/09/26 12:20:55 [ECDSAManager] Key should be an instance of *ecdsa.PrivateKey
Stream closed EOF for kubernetes-dashboard/kubernetes-dashboard-web-6ff79d4b57-pr824 (kubernetes-dashboard-web)

What did you expect to happen?

Certificates are generated and pod started.

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

Deploy standard kubernetes-dashboard via helm and edit kubernetes-dashboard-web deployment by adding - --auto-generate-certificates to args

Anything else we need to know?

No response

What browsers are you seeing the problem on?

No response

Kubernetes Dashboard version

1.4.0

Kubernetes version

Client Version: v1.31.1 Kustomize Version: v5.4.2 Server Version: v1.30.5

Dev environment

No response

@Michkov Michkov added the kind/bug Categorizes issue or PR as related to a bug. label Sep 26, 2024
@floreks floreks added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Sep 26, 2024
@floreks floreks self-assigned this Sep 26, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

4 participants