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

Collect PodDisruptionBudget metrics #3111

Merged
merged 3 commits into from
Feb 14, 2019
Merged

Collect PodDisruptionBudget metrics #3111

merged 3 commits into from
Feb 14, 2019

Conversation

xlucas
Copy link
Member

@xlucas xlucas commented Feb 13, 2019

What does this PR do?

Collect the following gauges reporting information about PodDisruptionBudget objects:

  • kubernetes_state.pdb.pods_desired
  • kubernetes_state.pdb.disruptions_allowed
  • kubernetes_state.pdb.pods_healthy
  • kubernetes_state.pdb.pods

Motivation

Allow tracking PDB information.

Review checklist

  • PR has a meaningful title or PR has the no-changelog label attached
  • Feature or bugfix has tests
  • Git history is clean
  • If PR impacts documentation, docs team has been notified or an issue has been opened on the documentation repo
  • If PR adds a configuration option, it has been added to the configuration file.

Additional Notes

Anything else we should know when reviewing?

@codecov
Copy link

codecov bot commented Feb 13, 2019

Codecov Report

Merging #3111 into master will decrease coverage by 2.96%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3111      +/-   ##
==========================================
- Coverage   84.83%   81.86%   -2.97%     
==========================================
  Files         681        4     -677     
  Lines       35675      353   -35322     
  Branches     4285       68    -4217     
==========================================
- Hits        30265      289   -29976     
+ Misses       4153       44    -4109     
+ Partials     1257       20    -1237

@bgeesaman
Copy link

Do you have a rough estimate of when this feature might make it into an agent release? We're trying to weigh options for using a custom solution or waiting for native integration. Thanks!

Copy link
Contributor

@xvello xvello left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM for the collection, two comments on the metadata

kubernetes_state.pdb.pods_desired,gauge,,,,Minimum desired number of healthy pods,0,kubernetes,k8s_state.pdb.pods_desired
kubernetes_state.pdb.disruptions_allowed,gauge,,,,Number of pod disruptions that are currently allowed,0,kubernetes,k8s_state.pdb.disruptions_allowed
kubernetes_state.pdb.pods_healthy,gauge,,,,Current number of healthy pods,0,kubernetes,k8s_state.pdb.pods_healthy
kubernetes_state.pdb.pods,gauge,,,,Total number of pods counted by this disruption budget,0,kubernetes,k8s_state.pdb.pods
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it make sense to rename it .pdb.pods_total for consistency with the other gauges, and being more explicit?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I concur as it would also be consistent with what one sees when using kubectl describe pdb ....

kubernetes_state/metadata.csv Outdated Show resolved Hide resolved
Copy link
Contributor

@xvello xvello left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@xlucas
Copy link
Member Author

xlucas commented Feb 14, 2019

@bgeesaman This should be in 6.10. Our target date for this release is week 9.

@xlucas xlucas merged commit 2edef7f into master Feb 14, 2019
@xlucas xlucas deleted the xavier.lucas/ksm-pdb branch February 14, 2019 14:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants