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.

Sign up for GitHub

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

Jump to bottom

Load your own certificate chain for dashboard? #2751

Closed
eroji opened this issue Jan 10, 2018 · 1 comment
Closed

Load your own certificate chain for dashboard? #2751

eroji opened this issue Jan 10, 2018 · 1 comment

Comments

@eroji
Copy link

eroji commented Jan 10, 2018

Environment
Dashboard version: 1.81
Kubernetes version: 1.91
Operating system: CentOS 7
Node.js version:
Go version:
Steps to reproduce

The default configuration for Kubernetes Dashboard does not provide any certificates. Is there a way to load your own certificate chain so that it can be properly controlled and presented by the ingress controller?
@floreks
Copy link
Member

floreks commented Jan 10, 2018

https://github.com/kubernetes/dashboard/wiki/Dashboard-arguments

There are cert related arguments that you can pass to load your own certificates. By default certs are auto-generated and stored inside the secret resource (kubernetes-dashboard-certs).

@floreks floreks closed this as completed Jan 10, 2018
VladimirAkopyan added a commit to VladimirAkopyan/dashboard that referenced this issue Nov 7, 2019
@VladimirAkopyan
Corrected Certificate installation incstructions
3a257c9 
The documentation is out of date. It suggests that certificates will be automatically picked up by the dashboard container, if they are named `dashboard.crt` and `dashboard.key`. This has caused a lot of confusion and multiple issues have been opened about this issue. 

kubernetes#2995
kubernetes#2751

I have provided instructions for editing deployment to add ` --tls-cert-file` and `--tls-key-file` arguments
I have renamed certificated to the defaults used by certmanger, as that's what most people will end up using. 
Please provide feedback if you are unhappy with this PR, but this needs to be corrected.
@VladimirAkopyan VladimirAkopyan mentioned this issue Nov 7, 2019
Merged
k8s-ci-robot pushed a commit that referenced this issue Nov 8, 2019
@VladimirAkopyan @k8s-ci-robot
Corrected Certificate installation incstructions (#4507)
31893b3 
The documentation is out of date. It suggests that certificates will be automatically picked up by the dashboard container, if they are named `dashboard.crt` and `dashboard.key`. This has caused a lot of confusion and multiple issues have been opened about this issue. 

#2995
#2751

I have provided instructions for editing deployment to add ` --tls-cert-file` and `--tls-key-file` arguments
I have renamed certificated to the defaults used by certmanger, as that's what most people will end up using. 
Please provide feedback if you are unhappy with this PR, but this needs to be corrected.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@floreks @eroji