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

UID for all the components in KSM #2115

Open
Gopinath-Selvam opened this issue Jul 8, 2023 · 5 comments
Open

UID for all the components in KSM #2115

Gopinath-Selvam opened this issue Jul 8, 2023 · 5 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@Gopinath-Selvam
Copy link

Gopinath-Selvam commented Jul 8, 2023

Request Kind:

Feature request

What would you like to be added:

Recently while working with KSM, I've came across a particular use case where UID's are needed for all the components for which metrics are exposed in KSM. So, would love it if there's ever a chance where UID for all the components are exposed along with their metrics.

Why is this needed:

This has been previously addressed here(Ref. here). This same use case applies to most of the components as well.

@Gopinath-Selvam Gopinath-Selvam added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 8, 2023
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jul 8, 2023
@Gopinath-Selvam
Copy link
Author

Would love to contribute for this as well if the Community/Maintainers find the above request useful!

@Gopinath-Selvam
Copy link
Author

Request Kind:

Feature request

What would you like to be added:

Recently while working with KSM, I've came across a particular use case where UID's are needed for all the components for which metrics are exposed in KSM. So, would love it if there's ever a chance where UID for all the components are exposed along with their metrics.

Why is this needed:

This has been previously addressed here(Ref. here). This same use case applies to most of the components as well.

Anybody checked this?

@logicalhan
Copy link
Member

/triage accepted
/assign

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jul 13, 2023
@mrueg
Copy link
Member

mrueg commented Jul 13, 2023

What are the implications on cardinality?

@k8s-triage-robot
Copy link

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

  • Confirm that this issue is still relevant with /triage accepted (org members only)
  • Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. and removed triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

5 participants