Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Ambiguity around the datadog-operator configuration with EKS addon

Open
  • Is something wrong?
#29,899 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
aws, helm, kubernetes
Domain
documentation

Research direction

Open the linked Operator EKS Add-on documentation page and compare its wording with the reported aws eks describe-addon-configuration output. Verify whether addon configuration overrides are supported, then clarify the documentation so the restriction and expected configuration behavior are unambiguous.

Written by the indexing model from the issue text.

Description

Documentation Page

https://docs.datadoghq.com/containers/guide/operator-eks-addon/

Issue Description

I recently tried to deploy a datadog-operator with AWS EKS addons.
Seeing the addon configuration schema, it says that the datadog operator EKS addon doesnt support configuration file. Here is the output of the aws eks describe-addon-configuration command:

{
    "addonName": "datadog_operator",
    "addonVersion": "v0.1.13-eksbuild.1",
    "configurationSchema": "{\"$schema\":\"https://json-schema.org/draft/2019-09/schema\",\"additionalProperties\":false,\"description\":\"No configuration support for datadog_operator\",\"type\":\"object\"}",
    "podIdentityConfiguration": []
}

But, based on the documentation here, it says something about the addon - "Operator Helm Chart values, which can be overridden, are restricted to a schema file.".

I understood from this sentence that the configuration for the addon could be overriden. Am I wrong? If so, can we improve the wording?

Dominant language
JavaScript
Stars
621
Forks
1.3k
Avg merge
2d 9h
Merged PRs (30d)
441

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DataDog/documentation

All issues in DataDog/documentation

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.