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

Support Agents +Integration+custom pipelines in own Space without admin permissions #132559

Open
zez3 opened this issue May 19, 2022 · 5 comments
Labels
Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@zez3
Copy link

zez3 commented May 19, 2022

Describe the feature:
Make Agents+Integrations (including custom pipelines) space aware

Describe a specific use case for the feature:
We've got some power users/sysadmins/DevOps(tenants like) that need to install their own Agents+APM and be able to customize the Policy Integrations that they deploy in their own Space without Elastic Admin permissions. They also need some custom pipelines.
Since sharable saved objects are already a thing, like @jen-huang mentioned here and @joshdover in #128202 (comment)
the need to allow users to share the same SO across multiple spaces would make sense here but I am not sure that it will cover all cases(like custom pipelines)

To clarify, other "tenants" in different spaces should not be able to interact with the Agents already deployed but assigned to other spaces or the other way around. Elastic Admins should.

At the moment I limit in roles the index access based on the namespace *my_namespace_tenant* and read-only for metrics-*my_namespace_tenant*
That works great for indices but for pipelines I need to give the bellow permission which are a bit too much as they could break some not belonging pipelines.
manage_enrich manage_pipeline read_pipeline manage_ingest_pipelines manage_logstash_pipelines manage

@botelastic botelastic bot added the needs-team Issues missing a team label label May 19, 2022
@jen-huang jen-huang added the Team:Fleet Team label for Observability Data Collection Fleet team label May 25, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@botelastic botelastic bot removed the needs-team Issues missing a team label label May 25, 2022
@zez3
Copy link
Author

zez3 commented Oct 13, 2022

any updates @joshdover ?

@zez3
Copy link
Author

zez3 commented Nov 9, 2022

@jamiehynds ?

@zez3
Copy link
Author

zez3 commented Nov 17, 2023

@nimarezainia

@nimarezainia
Copy link
Contributor

@zez3 we are looking at making Fleet space aware to the extent possible. but there will be limitations and we are working through those details at this point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

No branches or pull requests

4 participants