Skip to content

Allow specifying priorityClassName in datadog-operator#2468

Open
josh-ferrell wants to merge 1 commit intoDataDog:mainfrom
josh-ferrell:feat/datadog-operator-priorityclass
Open

Allow specifying priorityClassName in datadog-operator#2468
josh-ferrell wants to merge 1 commit intoDataDog:mainfrom
josh-ferrell:feat/datadog-operator-priorityclass

Conversation

@josh-ferrell
Copy link
Copy Markdown

@josh-ferrell josh-ferrell commented Mar 11, 2026

What this PR does / why we need it:

Allows the end user to configure the priorityClassName in the datadog-operator deployment.

Which issue this PR fixes

#1413

Special notes for your reviewer:

Checklist

[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

  • All commits are signed (see: signing commits)
  • Chart Version semver bump label has been added (use <chartName>/minor-version, <chartName>/patch-version, or <chartName>/no-version-bump)
  • For datadog or datadog-operator chart or value changes, update the test baselines (run: make update-test-baselines)

GitHub CI takes care of the below, but are still required:

  • Documentation has been updated with helm-docs (run: .github/helm-docs.sh)
  • CHANGELOG.md has been updated
  • Variables are documented in the README.md

@josh-ferrell josh-ferrell requested review from a team as code owners March 11, 2026 14:41
@josh-ferrell josh-ferrell changed the title Allow specifying priorityClassName Allow specifying priorityClassName in datadog-operator Mar 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant