When deploying the Datadog Helm chart (version 3.66.0), I encountered multiple warnings related to unrecognized or deprecated configuration keys in the /etc/datadog-agent/system-probe.yaml file of the datadog pods. The warnings appear to be associated with various runtime security configurations with the datadog pods.
2024-06-07 15:20:05 UTC | CORE | WARN | (pkg/config/setup/config.go:1729 in LoadCustom) | Unknown key in config file: runtime_security_config.network.enabled
2024-06-07 15:20:05 UTC | CORE | WARN | (pkg/config/setup/config.go:1729 in LoadCustom) | Unknown key in config file: runtime_security_config.activity_dump.cgroup_wait_list_size
2024-06-07 15:20:05 UTC | CORE | WARN | (pkg/config/setup/config.go:1729 in LoadCustom) | Unknown key in config file: runtime_security_config.activity_dump.path_merge.enabled
2024-06-07 15:20:05 UTC | CORE | WARN | (pkg/config/setup/config.go:1729 in LoadCustom) | Unknown key in config file: runtime_security_config.syscall_monitor.enabled
2024-06-07 15:20:05 UTC | CORE | WARN | (pkg/config/model/viper.go:192 in checkKnownKey) | config key runtime_security_config.activity_dump.path_merge.enabled is unknown
2024-06-07 15:20:05 UTC | CORE | WARN | (pkg/config/model/viper.go:192 in checkKnownKey) | config key runtime_security_config.activity_dump.cgroup_wait_list_size is unknown
2024-06-07 15:20:05 UTC | CORE | WARN | (pkg/config/model/viper.go:192 in checkKnownKey) | config key runtime_security_config.network.enabled is unknown
2024-06-07 15:20:05 UTC | CORE | WARN | (pkg/config/model/viper.go:192 in checkKnownKey) | config key runtime_security_config.syscall_monitor.enabled is unknown
2024-06-07 15:20:05 UTC | CORE | WARN | (pkg/config/model/viper.go:192 in checkKnownKey) | config key fips.enabled is unknown
2024-06-07 15:20:05 UTC | CORE | WARN | (pkg/config/model/viper.go:192 in checkKnownKey) | config key use_proxy_for_cloud_metadata is unknown
When deploying the Datadog Helm chart (version 3.66.0), I encountered multiple warnings related to unrecognized or deprecated configuration keys in the /etc/datadog-agent/system-probe.yaml file of the datadog pods. The warnings appear to be associated with various runtime security configurations with the datadog pods.