Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multi tenancy with with namespaces labels #6213

Open
2 of 3 tasks
arezvani opened this issue May 1, 2024 · 0 comments
Open
2 of 3 tasks

Multi tenancy with with namespaces labels #6213

arezvani opened this issue May 1, 2024 · 0 comments
Labels
question The question issue

Comments

@arezvani
Copy link

arezvani commented May 1, 2024

Is your question request related to a specific component?

vmauth, vmuser

Describe the question in detail

Hi, I have installed the Victoria Metrics operator along with all components (vminsert, vmselect, vmstorage, vmagent, and...). I then created vmauth and vmuser as per the examples provided. Everything is working fine, but I now wish to enable multi-tenancy. My goal is to have users with different endpoints, where each user can only view their own metrics. I aim to centralize Victoria Metrics and use a vmagent to collect all metrics, implementing this scenario with vmauth (using userNamespaceSelector and userSelector) and vmuser.

However, when I utilize vmauth (with userNamespaceSelector and userSelector) along with vmuser, I encounter an unauthorized error after entering the username and password in basic auth.

Is it possible to achieve this scenario with Victoria Metrics? What could be causing this issue? I would greatly appreciate any assistance or documentation related to this specific scenario.

Troubleshooting docs

@arezvani arezvani added the question The question issue label May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question The question issue
Projects
None yet
Development

No branches or pull requests

1 participant