-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Setup HTTPS for Kubernetes Dashboard #8964
Labels
kind/support
Categorizes issue or PR as a support question.
Comments
floreks
added
kind/support
Categorizes issue or PR as a support question.
and removed
kind/bug
Categorizes issue or PR as related to a bug.
labels
May 9, 2024
Provide some kind of logs/statuses from nginx, kong, and dashboard pods. This is most probably a configuration issue on your side. |
/close |
@floreks: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
Hi,
I recently installed kubernetes dashboard to serve for monitoring my cluster (Using helm chart). I setted up cluster and ingress nginx controller before. I sent below information, hope to receive support from everyone.
Ingress (true)
Kong (true)
What did you expect to happen?
You want to access "cluster-checking.sotaicg.com" domain through HTTPS. Then all components be installed completely. I curl my domain and it appear strange error. I can't think method to solve this problem
How can we reproduce it (as minimally and precisely as possible)?
No response
Anything else we need to know?
Before i install lastest version. I ran 1.2.7 version with secret and domain above and everything runs as I want
What browsers are you seeing the problem on?
No response
Kubernetes Dashboard version
latest
Kubernetes version
v1.28.9
Dev environment
No response
The text was updated successfully, but these errors were encountered: