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
I am deploying Pyroscope in Micro Service Mode in Kubernetes, below are my concerns
Does Pyroscope has login screen which can be either integrated with LDAP or atleast create few users with some credentials
and those users can login with the provided creds.
When deployed in Kubernetes Microservice mode, how to enable tls is unclear.
There is no documentation related to that or even when it is deployed in monolith mode.
I believe we can update the documentation with those details.
Can anyone please answer the above?
Thank you
Vikas
The text was updated successfully, but these errors were encountered:
Does Pyroscope has login screen which can be either integrated with LDAP or atleast create few users with some credentials
and those users can login with the provided creds.
We used to have an auth layer in pre-v1 versions but decided to remove it – we suggest that you implement the auth layer on your own. The simplest way is to deploy an authenticating reverse proxy (e.g., nginx) in front of the service, and limit the network access.
When deployed in Kubernetes Microservice mode, how to enable tls is unclear.
I'm afraid TLS is not fully supported at this time. We will address this issue in a future version.
I am deploying Pyroscope in Micro Service Mode in Kubernetes, below are my concerns
Does Pyroscope has login screen which can be either integrated with LDAP or atleast create few users with some credentials
and those users can login with the provided creds.
When deployed in Kubernetes Microservice mode, how to enable tls is unclear.
There is no documentation related to that or even when it is deployed in monolith mode.
I believe we can update the documentation with those details.
Can anyone please answer the above?
Thank you
Vikas
The text was updated successfully, but these errors were encountered: