-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Add label for priority class in kube_pod_info #712
Comments
Priority class is flat information on the Pod object, so adding the label to |
@chenk008: GitHub didn't allow me to assign the following users: chenk008. Note that only kubernetes members and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time. In response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@chenk008 go for it! :) |
Add label for priority class in kube_pod_info #712
* upstream/release-1.6: (90 commits) update documentation to reflect the latest release of kube-state-metrics *: Cut v1.6.0 *: Cut v1.6.0-rc.2 *: Cut v1.6.0-rc.1 bump versions of prometheus,kubernetes, and addon-resizer use appsv1 apigroup for StatefulSets and DaemonSets use xenial dist in travis ci use a more idiomatic way of handling error messages fix: change the expectedType of the kube-client reflector to match the listWatch Add list/watch access to ClusterRole for CSR collector docs: minor improvements in kube-state-metrics README *: Cut v1.6.0 README.md: Update compatibility matrix for kube-state-metrics v1.6 pkg/metrics_store: Cache byte slices instead of strings internal/collector: Preallocate metric slice length when known upfront change unit test change unit test fmt unit test Add unit test Add “priority_class” in document Add label for priority class in kube_pod_info kubernetes#712 ...
* upstream/release-1.6: (90 commits) update documentation to reflect the latest release of kube-state-metrics *: Cut v1.6.0 *: Cut v1.6.0-rc.2 *: Cut v1.6.0-rc.1 bump versions of prometheus,kubernetes, and addon-resizer use appsv1 apigroup for StatefulSets and DaemonSets use xenial dist in travis ci use a more idiomatic way of handling error messages fix: change the expectedType of the kube-client reflector to match the listWatch Add list/watch access to ClusterRole for CSR collector docs: minor improvements in kube-state-metrics README *: Cut v1.6.0 README.md: Update compatibility matrix for kube-state-metrics v1.6 pkg/metrics_store: Cache byte slices instead of strings internal/collector: Preallocate metric slice length when known upfront change unit test change unit test fmt unit test Add unit test Add “priority_class” in document Add label for priority class in kube_pod_info kubernetes#712 ...
* upstream/release-1.6: (90 commits) update documentation to reflect the latest release of kube-state-metrics *: Cut v1.6.0 *: Cut v1.6.0-rc.2 *: Cut v1.6.0-rc.1 bump versions of prometheus,kubernetes, and addon-resizer use appsv1 apigroup for StatefulSets and DaemonSets use xenial dist in travis ci use a more idiomatic way of handling error messages fix: change the expectedType of the kube-client reflector to match the listWatch Add list/watch access to ClusterRole for CSR collector docs: minor improvements in kube-state-metrics README *: Cut v1.6.0 README.md: Update compatibility matrix for kube-state-metrics v1.6 pkg/metrics_store: Cache byte slices instead of strings internal/collector: Preallocate metric slice length when known upfront change unit test change unit test fmt unit test Add unit test Add “priority_class” in document Add label for priority class in kube_pod_info kubernetes#712 ...
Is this a BUG REPORT or FEATURE REQUEST?:
/kind feature
What happened:
It would be nice to be able to have information about the priority class to write alerts that does not involve low priority pods.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version
): 1.13.5The text was updated successfully, but these errors were encountered: