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

Manage Organisations and Teams with CR #549

Closed
Voigtus opened this issue Oct 3, 2021 · 1 comment
Closed

Manage Organisations and Teams with CR #549

Voigtus opened this issue Oct 3, 2021 · 1 comment
Labels
enhancement New feature or request triage/duplicate Indicates an issue is a duplicate of other open issue.

Comments

@Voigtus
Copy link
Contributor

Voigtus commented Oct 3, 2021

Is your feature request related to a problem? Please describe.
We deploy the Grafana Operator to OpenShift. Right now it is only for us as an infrastructure team. But, looking further down the line, we can imagine to grant access to our Grafana or provide it "as service" for different OpenShift clusters of teams and tenants.
To regulate the access to specific teams or tenants the Organization (Orgs) and Teams feature of Grafana would be quite helpful.

Describe the solution you'd like
My "happy-go-lucky" solution would be a CRD for either Teams and Orgs, that are used by the operator to generate both. As per documentation of Grafana the go-to way would be to use the /api/orgs/ endpoint and generate these via API and the admin account.

Describe alternatives you've considered
Right now we are considering to run a Job triggered by the "Post-Sync" hook of ArgoCD and create the Orgs via API-calls ourself.
We try to remove all manual input of us after cluster creation, therefore manual "administration" is a no-go

If this is something "accepted" by the community I would like to implement this feature, since it would greatly benefit us.

@Voigtus Voigtus added enhancement New feature or request needs triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 3, 2021
@NissesSenap
Copy link
Collaborator

Duplicate of: #408
As written in 408, it's nothing that we are currently prioritizing but if you feel like taking a stab at it we love to get a PR.
As a workaround we could also use your Post-Sync hooks in ArgoCD as documentation, I think some users would find this as a good start as well :)

@NissesSenap NissesSenap added triage/duplicate Indicates an issue is a duplicate of other open issue. and removed needs triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request triage/duplicate Indicates an issue is a duplicate of other open issue.
Projects
None yet
Development

No branches or pull requests

2 participants