Pinned to datadog-agent v7.28.0-rc.5
- The cluster-agent container now tries to remove any folder beginning by
..in paths of files mounted in/conf.dwhile copying them to the cluster-agent config folder - collect cluster resource for orchestrator explorer.
- It's now possible to template the kube_cluster_name tag in DatadogMetric queries Example: avg:nginx.net.request_per_s{kube_container_name:nginx,kube_cluster_name:%%tag_kube_cluster_name%%}
- It's now possible to template any environment variable (as seen by the Datadog Cluster Agent) as tag in DatadogMetric queries Example: avg:nginx.net.request_per_s{kube_container_name:nginx,kube_cluster_name:%%env_DD_CLUSTER_NAME%%}
- It is now possible to configure a custom timeout for the MutatingWebhookConfigurations objects controlled by the Cluster Agent via DD_ADMISSION_CONTROLLER_TIMEOUT_SECONDS. (Default: 30 seconds)
- The Datadog Cluster Agent's Admission Controller now uses a namespaced secrets informer. It no longer needs permissions to watch secrets at the cluster scope.
- The cluster agent now uses the same configuration than the security agent for the logs endpoints configuration. The parameters (such as logs_dd_url can be either be specified in the compliance_config.endpoints section or through environment variables (such as DD_COMPLIANCE_CONFIG_ENDPOINTS_LOGS_DD_URL).
- Improve the resilience of the connection of controllers to the External Metrics Server by moving to a dynamic client for the WPA controller.
- Change base Docker image used to build the Cluster Agent imges, moving from debian:bullseye to ubuntu:20.10. In the future the Cluster Agent will follow Ubuntu stable versions.
- Fix a potential file descriptors leak.
- The Cluster Agent can now be configured to use tls 1.2 via DD_FORCE_TLS_12=true
- Fix "Error creating expvar server" error log when running the Datadog Cluster Agent CLI commands.
- Fix a bug preventing the "DD_ORCHESTRATOR_EXPLORER_ORCHESTRATOR_ADDITIONAL_ENDPOINTS" environment variable to be read.
Released on: 2021-03-02 Pinned to datadog-agent v7.26.0: CHANGELOG.
- Support Prometheus Autodiscovery for Kubernetes Services.
- Add external_metrics_provider.api_key and external_metrics_provider.app_key parameters overriding default api_key and app_key if set.
- Add a new external_metrics_provider.endpoint config in datadog-cluster.yaml and a DD_EXTERNAL_METRICS_PROVIDER_ENDPOINT environment variable to override the default Datadog API endpoint to query external metrics from, in place of the global DATADOG_HOST. It also makes the external metrics provider respect DD_SITE if DD_EXTERNAL_METRICS_PROVIDER_ENDPOINT is not set.
- Node schedulability is now a dedicated tag on kubernetes node resources.
- Fix dual shipping for orchestrator resources in the cluster agent.
- Released on: 2021-03-02
- Pinned to datadog-agent v7.24.0: CHANGELOG..
- Add a new command 'datadog-cluster-agent health' to show the cluster agent's health, similar to the already existing agent health.
- collect node information for the orchestrator explorer
- Fill DatadogMetric AutoscalerReferences field to ease usage/investigation of DatadogMetrics
- The Cluster Agent can now collect stats from Cluster Level Check runners to optimize its dispatching logic and rebalance the scheduled checks.
- Allow providing custom tags to orchestrator resources.
- Add new configuration parameter to allow 'GroupExec' permission on the secret-backend command. The new parameter ('secret_backend_command_allow_group_exec_perm') is now enabled by default in the cluster-agent image.
- Add resolve option to endpoint checks through new annotation ad.datadoghq.com/endpoints.resolve. With ip value, it allows endpoint checks to target static pods
- Expose metrics for the cluster level checks advanced dispatching.
- Fix 'readsecret.sh' permission in Cluster-Agent dockerfiles that removes other permission.
- Fix issue in Cluster Agent when using external metrics without DatadogMetrics where multiple HPAs using the same metricName + Labels would prevent all HPAs (except 1st one) to get values from Datadog
- Ensure that leader election runs if orchestrator_explorer and leader_election are enabled.
- Rename node role tag from "node_role" to "kube_node_role" in orchestrator_explorer collection.
Released on: 2020-10-21 Pinned to datadog-agent v7.23.1: CHANGELOG..
- Support of secrets in JSON environment variables, added in 7.23.0, is reverted due to a side effect (e.g. a string value of "-" would be loaded as a list). This feature will be fixed and added again in a future release.
Released on: 2020-10-13 Pinned to datadog-agent v7.23.0: CHANGELOG..
- Collect the node and cluster resource in Kubernetes for the Orchestrator Explorer (#6297).
- Add resolve option to the endpoint checks (#5918).
- Add health command (#6144).
- Add options to configure the External Metrics Server (#6406).
- Fill DatadogMetric AutoscalerReferences field to ease usage/investigation of DatadogMetrics (#6367).
- Only run compliance checks on the Cluster Agent leader (#6311).
- Add orchestrator_explorer configuration to enable the cluster-id ConfigMap creation and Orchestrator Explorer instanciation (#6189).
- Fix transformer for gibiBytes and gigaBytes (#6437).
- Fix cluster-agent commands to allow executing the readsecret.sh script for the secret backend feature (#6445).
- Fix issue with External Metrics when several HPAs use the same query (#6412).
Released on: 2020-08-07
- Add compliance check command to the DCA CLI (#5930)
- Add clusterchecks rebalance command (#5839)
- Add collection of additional Kubernetes resource types (deployments, replicaSets and services) for Live Containers (#6082, #5999)
- Support "ignore AD tags" parameter for cluster/endpoint checks (#6115)
- Use APIserver connection retrier (#6106)
Released on: 2020-07-20
This version contains the changes released with version 7.21.0 of the core agent. Please refer to the CHANGELOG.
- Add support of DatadogMetric CRD to allow autoscaling based on arbitrary queries (#5384)
- Add Admission Controller to inject Entity ID, standard tags and agent host (useful in serverless environments)
- Add leader_election_is_leader metric to allow label joins (#5819)
Released on: 2020-06-11
This version contains the changes released with version 7.20.0 of the core agent. Please refer to the CHANGELOG.
- Wait for client-go cache to sync for endpoints/services (#5291)
- Consider check failure in advanced rebalancing (#5441)
- Autodiscover standard tags for Cluster and Endpoint Checks (#5241)
- Adds a metric to monitor the advanced dispatching algorithm (#4970)
Released on: 2020-02-11
Minor release on 1.5 branch
- Fix agent commands in DCA (always start listener) (#4870)
Released on: 2020-02-06
Minor release on 1.5 branch
- [DCA] fix cluster-agent flare panic (#4838)
- Remove setcap NET_BIND_SERVICE as we cannot make it work with user namespaces used in the CI (#4846)
- Add service listener in endpoints to watch for newly annotated services (#4816)
- Fix typo (#4831)
Released on: 2020-01-28
This version contains the changes released with version 7.17.0 of the core agent. Please refer to the CHANGELOG.
- Adding logic to show DCA status for clc (#4738)
- Introduce Rate Limiting Stats in the /metrics of the Cluster Agent (#4669)
- MetricServer generates k8s event on HPA
- Add cluster-name tag in host tags (#4558)
- Add read-secret command in cluster-agent to use as secrets backend (#4639)
- Adding logic to show DCA status for clc (#4738)
- Allow dots in cluster names (#4611)
- Check if CheckMetadata exist before iterating over it in cluster agent status page (#4728)
- Grant CAP_NET_BIND_SERVICE capability to the cluster_agent (#4439)
- Ignore invalid cluster names instead of panicking (#4549)
- Fix eventrecorder init (#4732)
- Handle NewHandler failure better in setupClusterCheck (#4447)
- Adding User-Agent to the DCA client
- Filter non-cluster-checks (#4566)
Released on: 2019-11-06
This version contains the changes released with version 6.15.0 of the core agent. Please refer to the CHANGELOG.
- Introducing the Advanced dispatching logic to rebalancing Cluster Level Checks [#4068, #4226, #4344]
- Enable the Endpoint check logic [#3853, #3704]
- HTTP proxy support for the external metrics provider #4191
- Improve External Metrics Provider resiliency [#4285, #3727]
- Revamp the Kubernetes event collection check [#4259, #4346, #4342, #4337, #4314]
- Update Gopkg.lock with new import #3837
- Fix kubernetes_apiserver default config file #3854
- Fix registration of the External Metrics Server's API #4233
- Fixing status of the Cluster Agent if the External Metrics Provider is not enabled #4277
- Fix how the endpoints check source is displayed in agent command outputs #4357
- Fix how we invalidate changed Endpoints config #4363
- Get Cluster Level Checks runner IPs from headers #4386
- Fixing output of agent status #4352
2019-07-09
- Fix Cluster-agent failure with cluster-agent flare command.
2019-06-19
- Fix "Kube Services" service: kube service tags attached to pod are not consistent.
Released on: 2019-05-07
The Datadog Cluster Agent can now auto-discover config templates for kubernetes endpoints checks and expose them to node Agents via its API. This feature is compatible with the version 6.12.0 and up of the Datadog Agent.
Refer to the official documentation to read more about this feature.
2019-05-03
- Fix race condition: immutable MetaBundle stored in DCA cache.
2019-04-30
- Fix race condition in Cluster Agent's API handler.
2019-04-24
- The Cluster Agent can now auto-discover config templates for kubernetes endpoints checks and expose them to node Agents via its API
- Add the
configandconfigcheckcommand to the cluster agent CLI - Add the
diagnosecommand to the cluster agent CLI and flare - Add cluster_checks.extra_tags option to allow users to add tags globally to the cluster level checks.
- Improving Lifecycle of the External Metrics Provider
- Support milliquantities for the External Metrics Provider
- Move some logs from info to debug, in order to generates fewer noisy logs when running correctly.
Released on: 2019-02-25
The Datadog Agent now supports distributing Cluster Level Checks. This feature is compatible with the version 6.9.0 and up of the Datadog Agent.
Refer to the official documentation to read more about this feature.
2019-02-14
- Ensure dangling cluster checks can be re-scheduled
2019-02-12
- Fix re-scheduling of the same clusterchecks config on the same node
2019-02-11
- Sign docker images when pushing to Docker Hub
- Fix configcheck verbose output
- Fix AutoDiscovery rescheduling issue when no template variables
- Remove resolved configs when template are removed
- Support adding/removing the AD annotation to an existing kube service
- Only expose cluster-check prometheus metrics when leading
- Fix support for custom metrics case sensitivity
2019-02-05
The External Metrics Provider is now agnostic of the case, both on the metric name and the labels extracted from HPAs.
- Cluster Agent HPA metrics case support
- Add GetLeaderIP method to LeaderEngine
- Add kube_service config provider
- Allow to set additional Autodiscovery sources by envvars
- Add dispatching metrics in clusterchecks module
- Add a health probe in the ccheck dispatching logic
- Add kube-services AD listener
- Cluster-checks: handle leader election and follower->leader redirection
- Enable clusterchecks in DCA master
- Support /conf.d in cluster-agent image
- Fix clustercheck leader not starting its dispatching logic
- Use the appropriate port when redirecting node-agents to leader
- Cluster-checks: patch configurations on schedule
- Add configcheck/config cmd on the cluster agent
- Add clustercheck info to the cluster-agent's status and flare
- Make error in clusterchecks cmd clear when feature is disabled
2019-01-31
The release of the RC1 was dismissed to embed a fix for the CI runners used to build the image. - Go 1.11.5 compliancy + 1.11.5 for every CI The official release of the Datadog Cluster Agent 1.2.0 starts with the RC2.
The version 1.1.0 of the Cluster Agent introduces new features and enhancements around the External Metrics Provider.
2018-11-21
- Get goautoneg from github
- Fix datadog external metric query when no label is set
2018-11-20
- Migrating back to official custom metrics lib
- Change test to remove flakiness
- Disable cluster checks in cluster-agent 1.1.x
- Allow users to change the custom metric provider port, to run as non-root
- Adding rollup and fix to circumvent time aggregation
- clusterchecks: simple dispatching logic
- Honor external metrics provider settings in cluster-agent status
- Run cluster-agent as non-root, support read-only rootfs
- Only push cluster-agent-dev:master from master
- Fix folder permissions on containerd
- Adding fix for edge case in external metrics
- Fix flare if can't access APIServer
- DCA: fix custom metrics server
- Avoid panicking for missing fields in HPA
Released on: 2018-10-18
The Datadog Cluster Agent is compatible with versions 6.5.1 and up of the Datadog Agent.
- Please refer to the 6.5.0 tag on datadog-agent for the list of changes on the Datadog Agent.
It is only supported in containerized environments.
- Please find the image on our Docker Hub.
2018-10-17
- Expose telemetry metrics with the Open Metrics format instead of expvar
- add mutex logic and safe guards to avoid race condition in the Autoscalers Controller.
2018-10-15
- Leverage diff logic to only update the internal custom metrics store and Config Map with relevant changes.
- Better logging on the Autoscalers Controller
- Make sure only the leader sync Autoscalers.
- Forget keys from the informer's queue to avoid borking the Autoscalers Controller.
2018-10-11
- Support agent and datadog-cluster-agent for the CLI of the Datadog Cluster Agent
- Retrieve hostname in GCE
2018-10-04
- Implement the External Metrics Interface to allow for the Horizontal Pod Autoscalers to be based off of Datadog metrics.
- Use informers to be up to date with the Horizontal Pod Autoscalers object in the cluster.
- Implement the metadata mapper.
- Use informers to be up to date with the Endpoints and Nodes objects in the cluster.
- Serve cluster level metadata on an external endpoint, kube_service tag is available.
- Serve node labels as tags.
- Run the kube_apiserver check to collect events and run a service check against each component of the Control Plane.
- Implements the flare, status and version commands similar to the node agent.