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

NodeMetrics is currently marked as Namespaced should be cluster scoped #3662

Closed
manusa opened this issue Dec 17, 2021 · 0 comments · Fixed by #3688
Closed

NodeMetrics is currently marked as Namespaced should be cluster scoped #3662

manusa opened this issue Dec 17, 2021 · 0 comments · Fixed by #3688
Assignees
Labels
Milestone

Comments

@manusa
Copy link
Member

manusa commented Dec 17, 2021

Also related to this is that NodeMetrics is currently marked as Namespaced, and it should not be.

Originally posted by @shawkins in #3639 (comment)

@manusa manusa added the bug label Dec 17, 2021
@shawkins shawkins mentioned this issue Dec 17, 2021
11 tasks
rohanKanojia added a commit to rohanKanojia/kubernetes-client that referenced this issue Dec 23, 2021
…source

NodeMetrics should not implement Namespaced interface

Signed-off-by: Rohan Kumar <[email protected]>
rohanKanojia added a commit to rohanKanojia/kubernetes-client that referenced this issue Dec 23, 2021
…source

NodeMetrics should not implement Namespaced interface

Signed-off-by: Rohan Kumar <[email protected]>
@manusa manusa added this to the 5.11.1 milestone Dec 23, 2021
Repository owner moved this from Review to Done in Eclipse JKube - Sprint #211 + Sprint #212 (2021-12-01 → 2022-01-11) Dec 24, 2021
manusa pushed a commit that referenced this issue Dec 24, 2021
NodeMetrics should not implement Namespaced interface

Signed-off-by: Rohan Kumar <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants