Skip to content

feat(orchestrator): collect Gateway and Inference API resources by default - #55888

Draft
aureleoules wants to merge 2 commits into
mainfrom
codex/collect-gateway-inference-api-resources
Draft

feat(orchestrator): collect Gateway and Inference API resources by default#55888
aureleoules wants to merge 2 commits into
mainfrom
codex/collect-gateway-inference-api-resources

Conversation

@aureleoules

@aureleoules aureleoules commented Sep 4, 2026

Copy link
Copy Markdown
Member

What does this PR do?

Collects standard Gateway API and Gateway API Inference Extension custom resources in Orchestrator Explorer by default, with fallbacks for versions served by older releases. It preserves the existing gateway_api opt-out and avoids duplicate collection when the same resource is configured explicitly at another version.

It also makes version discovery resource-aware and adds an orchestrator E2E covering HTTPRoute and InferencePool manifests.

Motivation

Make Gateway and inference-routing topology available without manual collector configuration.

Backend allowlisting and default RBAC are supplied by the companion dd-go, Operator, Helm, and internal Operator chart PRs. Those dependencies must roll out before the Agent release.

Companion PRs:

Describe how you validated your changes

  • dda inv test --targets=./pkg/collector/corechecks/cluster/orchestrator/...
  • dda inv linter.go --targets=./pkg/collector/corechecks/cluster/orchestrator,./pkg/collector/corechecks/cluster/orchestrator/discovery
  • dda inv linter.go --module=test/new-e2e --targets=./tests/orchestrator
  • bazel run //bazel/buildifier
  • bazel build //test/new-e2e/tests/orchestrator:orchestrator_test
  • YAML and release-note validation

The cloud E2E was not provisioned locally; the existing orchestrator CI job will run it.

Additional Notes

Set orchestrator_explorer.custom_resources.ootb.gateway_api to false to opt out.

@aureleoules aureleoules added qa/done QA done before merge and regressions are covered by tests short review PR is simple enough to be reviewed quickly team/kubernetes-experiences internal Identify a non-fork PR labels Sep 4, 2026
@github-actions github-actions Bot added long review PR is complex, plan time to review it and removed short review PR is simple enough to be reviewed quickly labels Sep 4, 2026

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

AI review by Codex (OpenAI) - workflow run

patch is correct — the changed skill is well-scoped, clearly triggered, owned, concise, and defines a verifiable release-note workflow.

---
name: create-release-note
description: Create a reno release note for a PR or change
description: Create a reno release note for a PR or change. Use when asked to create, add, or write a release note or changelog entry.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Skill assessment — Priority 3

  • Description (triggering): 23/25
  • Writing philosophy: 21/25
  • Structure and progressive disclosure: 25/25
  • Output definition and examples: 23/25
  • Total: 92/100
  • Recommendation: Approve

Top actionable improvements:

  1. Narrow the description further by mentioning Datadog Agent/reno release notes, reducing accidental triggers for unrelated changelog systems.
  2. Add a short rationale for the section-selection and APM-prefix rules so future maintainers understand the underlying constraints.
  3. Add one complete input-to-generated-YAML example; the current command, template, and examples are useful but distributed across sections.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal Identify a non-fork PR long review PR is complex, plan time to review it qa/done QA done before merge and regressions are covered by tests team/agent-devx team/fleet-automation team/kubernetes-experiences

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant