datadog-operator icon indicating copy to clipboard operation
datadog-operator copied to clipboard

Datadog Agent Kubernetes Operator

Results 262 datadog-operator issues
Sort by recently updated
recently updated
newest added

### What does this PR do? Add `otlp` feature to configure [OTLP ingest](https://docs.datadoghq.com/tracing/trace_collection/open_standards/otlp_ingest_in_the_agent/?tab=host). ### Motivation Allow users to configure this feature via the Datadog operator. ### Additional Notes Configuration has...

enhancement

### What does this PR do? A brief description of the change being made with this pull request. ### Motivation What inspired you to submit this pull request? ### Additional...

enhancement
component/controller

### What does this PR do? This implements the overrides defined in a `v2alpha1.DatadogAgentComponentOverride` object. The overrides are mostly about the pod template specs, but they also affects deployments, and...

enhancement

Currently the Datadog Operator configuration does not cater for Kubernetes clusters located behind proxy servers. [A pull request ](https://github.com/DataDog/datadog-operator/pull/532)was made to address this.

documentation
enhancement
stale

### What does this PR do? #435 renamed `docs/configuration.md` to `docs.configuration.v1alpha1.md`, but that broke links to that page. This fixes the links. I also noticed that the example manifest in...

documentation

**Describe what happened:** I deployed Datadog Operator Helm chart version `0.8.5` and `DatadogAgent`. The cluster agent doesn't send `kubernetes_state` (or `kuberenetes_state_core`) metrics to Datadog. When I run `agent status` on...

**Describe what happened:** Provisioning new `DatadogAgent` resources with `spec.agent.apm.unixDomainSocket.enabled: true` creates a socket under `/var/run/datadog/apm.sock`, which contradicts most client libraries default lookup path of `/var/run/datadog/apm.socket` (`socket` not `sock`). **Describe what...

**Output of the info page (if this is a bug)** ``` │ Args: │ │ │ -supportExtendedDaemonset=false │ │ │ -logEncoder=json │ │ │ -metrics-addr=:8383 │ │ │ -loglevel=info │...

stale

Could it be that `NodeSelector` for `clusterChecksRunner` is not implemented yet?

stale

### What does this PR do? Implements a finalizer for V2 agents. The finalizer removes all the resources associated with the agent. Before this PR, cluster roles and cluster role...

bug