-
Notifications
You must be signed in to change notification settings - Fork 1.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
Collect PodDisruptionBudgets in Cluster Agent #30412
Conversation
44691d6
to
dc89011
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like a word or two was missing.
releasenotes/notes/cluster-agent-collect-pod-disruption-budget-5d8cf316c3633684.yaml
Outdated
Show resolved
Hide resolved
1162e01
to
aca050e
Compare
Test changes on VMUse this command from test-infra-definitions to manually test this PR changes on a VM: inv create-vm --pipeline-id=48142890 --os-family=ubuntu Note: This applies to commit 063f429 |
pkg/collector/corechecks/cluster/orchestrator/collectors/k8s/poddisruptionbudget.go
Outdated
Show resolved
Hide resolved
aca050e
to
3882e2f
Compare
Regression Detector |
3882e2f
to
820ab55
Compare
820ab55
to
121d517
Compare
NOTE: not adding yaml - all the yaml fields are marked as obsolete and we now have a dedicated pipeline for yamls so I presume there is no need to add the field
121d517
to
2bcb7f7
Compare
2bcb7f7
to
063f429
Compare
/merge |
🚂 MergeQueue: pull request added to the queue The median merge time in Use |
What does this PR do?
Collect PodDisruptionBudgets in Cluster Agent.
Motivation
Collect PDB information.
Describe how to test/QA your changes
Tested locally:
The agent reports observing the PDB, doesn't crash.
TDB: verify no change in CPU load.
Possible Drawbacks / Trade-offs
Additional Notes
Needs DataDog/agent-payload#351 to be submitted and pulled in properly before this can be submitted.