You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we do not validate the configuration file coming from the user. The same goes for server config as well. I am not sure we should implement validation for server config but we should do it for the config file.
For example, when a user does not provide information for admin, we do not open port for /metrics, /ready /pprof/ endpoints and users cannot access those endpoints.
The text was updated successfully, but these errors were encountered:
For example, when a user does not provide information for admin, we do not open port for /metrics, /ready /pprof/ endpoints and users cannot access those endpoints.
I think these ports should always be available, just use port 80 and 8081 as default ports for them
Currently, we do not validate the configuration file coming from the user. The same goes for server config as well. I am not sure we should implement validation for server config but we should do it for the config file.
For example, when a user does not provide information for admin, we do not open port for /metrics, /ready /pprof/ endpoints and users cannot access those endpoints.
The text was updated successfully, but these errors were encountered: