-
|
I am using Quarkus successfully deploying to a local k8s cluster for development, and the live code reloading all works fine (and is great). However, I would also like to be able to use the dev ui but it doesn't seem to be available and I can't find any configuration options that can be set to make it available. Am I just missing something? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 12 replies
-
Beta Was this translation helpful? Give feedback.
-
Are you using remote dev mode? |
Beta Was this translation helpful? Give feedback.
-
|
We are being very conservative with anything not related to dev mode. That said, we could of course consider such things |
Beta Was this translation helpful? Give feedback.
-
|
FYI the reason it's turned of for remote dev is that you then most likely have a endpoint where you are able to browse security keys. Ie. A security risk. |
Beta Was this translation helpful? Give feedback.
-
|
Would it be possible/acceptable to expose q/dev on an alternative port that is not made available to the world? This port could be exposed as a ClusterIP-service and to access the service the developer could use |
Beta Was this translation helpful? Give feedback.
-
|
I'm new to Quarkus and was assuming this was something broken in my setup. Could the Dev UI in remote mode perhaps instead display a message like "Dev UI not available in remote-dev mode", or similar? Also, for me (like I suspect a lot of other people using remote-dev) the "remote" development environment is actually a local Kubernetes cluster, and so the fears about opening sensitive data to the world don't apply so much, so maybe there could be a configuration parameter to enable the Dev UI? |
Beta Was this translation helpful? Give feedback.
-
I think this makes sense |
Beta Was this translation helpful? Give feedback.
Are you using remote dev mode?