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

Define K8s_Processor RBAC Setup requirements #2274

Closed
ericmustin opened this issue Feb 2, 2021 · 4 comments
Closed

Define K8s_Processor RBAC Setup requirements #2274

ericmustin opened this issue Feb 2, 2021 · 4 comments
Labels
closed as inactive documentation Improvements or additions to documentation priority:p2 Medium release:required-for-ga Must be resolved before GA release Stale

Comments

@ericmustin
Copy link
Contributor

Hello friends,

As we approach the "1.0" phase of tracing, we've noticed a fair number of users looking to leverage the k8s_processor in the collector setup. RBAC is a common pain point here, it would be good to improve the documentation and define what requirements are needed. it seems like there are some open TODOs in this regard and if there's any clarity on timeline or roadmap here that would help greatly.

// RBAC
//
// TODO: mention the required RBAC rules.

@flands
Copy link
Contributor

flands commented Feb 7, 2021

@owais @jrcamp can we get this added?

@flands flands added documentation Improvements or additions to documentation priority:p2 Medium release:required-for-ga Must be resolved before GA release labels Feb 7, 2021
ljmsc referenced this issue in ljmsc/opentelemetry-collector-contrib Feb 21, 2022
…ty (#2274)

* Rename ExportKind to aggregation.Temporality

* Changelog uhhhhhhh

* Apply suggestions from code review

Co-authored-by: Tyler Yahn <[email protected]>

* int->uint8

* go generate

* go.sum

* anual edit

Co-authored-by: Tyler Yahn <[email protected]>
@omamoo
Copy link

omamoo commented Mar 2, 2022

Can someone attach the RBAC he uses?

@github-actions
Copy link
Contributor

github-actions bot commented Nov 8, 2022

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

@github-actions github-actions bot added the Stale label Nov 8, 2022
@github-actions
Copy link
Contributor

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed as inactive documentation Improvements or additions to documentation priority:p2 Medium release:required-for-ga Must be resolved before GA release Stale
Projects
None yet
Development

No branches or pull requests

3 participants