Self-hosted dashboard operators lack flexible access controls
Operators of self-hosted rollout and monitoring dashboards want private admin views, often with OIDC sign-in, without necessarily making status or shared dashboards private. Reports for Argo Rollouts and Uptime Kuma describe missing built-in authentication or SSO; one Argo Rollouts user said they avoided exposing the dashboard and used ArgoCD’s promote function as a workaround. The Grafana request also points to the need for configurable anonymous access, rather than requiring every dashboard to have the same access policy.
For self-hosted dashboard and DevOps operators. Mentioned from Oct 2021 to Jan 2023 on GitHub.
6 different people described this problem in 3 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 6.3/10
- Frequency
- 7.0/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
Not having dashboard authentication when installed on the cluster is major blocker for customers using rollouts in production clusters
Really like the Rollouts dashboard, but I cannot public it to the outside because of lacking authentication > > Currently, I am using the promote function of ArgoCD as a workaround
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 5 places to find your first customers
- 5 more quotes from people who have this problem
- Current workarounds, existing solutions and risks