Add Kueue workload events

[gjulianm]

What does this PR do?

Adds optional Kueue Workload lifecycle event collection for created, quota reserved, admitted, running, evicted, and finished transitions.

Motivation

Surface workload scheduling and eviction changes in Datadog events for operators monitoring Kueue queues.

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Add qa/required if this PR needs QA validation, or qa/skip-qa if it does not. Exactly one of the two is required.
• If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

[datadog-official]

 

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 80.84%
• Overall Coverage: 81.32% (-6.73%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 7768aaf | Docs | Datadog PR Page | Give us feedback!}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: cafad0b4aa

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[mbertrone]

LGTM. A few notes inline; the only one worth fixing before merge is the two suppression tests, which currently can't fail.

Review from mbertrone is dismissed. Related teams and files:

• gpu-monitoring-agent
  • kueue/datadog_checks/kueue/check.py
  • kueue/datadog_checks/kueue/kube_client.py
  • kueue/tests/test_unit.py

[mbertrone]

issue (blocking): this call blows up with 'NoneType' object has no attribute 'collect_workload_events' (the failure CI is already reporting for test_e2e_workload_events). The config-model fix from this review round changed _parse_workload_events_config to read self.config.collect_workload_events (check.py:148), but self.config returns self._config_model_instance, which AgentCheck.__init__ initializes to None and only load_configuration_models populates. That initializer is registered in check_initializations and runs inside run(), so on the normal path it fires before _parse_workload_events_config. Here you call _parse_workload_events_config() by hand right after construction, before any initialization has run, so self.config is still None. Production is unaffected; only this manual invocation trips it.

Load the model first:

check = KueueCheck('kueue', {}, [load_check_instance(kubeconfig_dict)])
check.load_configuration_models()
check._parse_workload_events_config()
check.check(check.instance)

[dd-octo-sts]

Validation Report

All 21 validations passed.

Show details

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and code coverage settings	✅
codeowners	Validate every integration has a CODEOWNERS entry	✅
config	Validate default configuration files against spec.yaml	✅
dep	Verify dependency pins are consistent and Agent-compatible	✅
http	Validate integrations use the HTTP wrapper correctly	✅
imports	Validate check imports do not use deprecated modules	✅
integration-style	Validate check code style conventions	✅
jmx-metrics	Validate JMX metrics definition files and config	✅
labeler	Validate PR labeler config matches integration directories	✅
legacy-signature	Validate no integration uses the legacy Agent check signature	✅
license-headers	Validate Python files have proper license headers	✅
licenses	Validate third-party license attribution list	✅
metadata	Validate metadata.csv metric definitions	✅
models	Validate configuration data models match spec.yaml	✅
openmetrics	Validate OpenMetrics integrations disable the metric limit	✅
package	Validate Python package metadata and naming	✅
qa-label	Validate the pull request declares whether it needs QA for the next Agent release	✅
readmes	Validate README files have required sections	✅
saved-views	Validate saved view JSON file structure and fields	✅
version	Validate version consistency between package and changelog	✅

View full run