Replies: 3 comments 1 reply
-
any update? |
Beta Was this translation helpful? Give feedback.
1 reply
-
In my environment I was able to make work using nginx ingress controller like this:
It redirects just fine. The only problem it's my cert: |
Beta Was this translation helpful? Give feedback.
0 replies
-
Can you paste your ingress in yaml format here? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I upgraded to the 7.5.0 release of the helm chart for the k8s-dashboard. I am getting "400 Bad Request
The plain HTTP request was sent to HTTPS port" when loading the webpage for the UI in my browser.
I expected to see a login page where I can supply a token.
I did clean installation for the new helm chart with ingress enabled and a couple parameters defined such as annotations, ingress class name, host and lets-encrypt for ssl connection, but when trying to access the dashboard UI in my browser, I got "400 Bad Request ..."
These are the values that I am supplying to the helm chart:
I would like to be able to reach the dashboard UI from outside the cluster via Https protocol with custom host.
so what should be configured or how would I point to kong proxy when using the ingress provided in the helm chart?
If there is any other information I can provide, please let me know. Thank you for your help!
Beta Was this translation helpful? Give feedback.
All reactions