-
Notifications
You must be signed in to change notification settings - Fork 16.7k
[stable/datadog] Support custom check definitions for CLC Runners #23139
[stable/datadog] Support custom check definitions for CLC Runners #23139
Conversation
Hi @juliogreff. Thanks for your PR. I'm waiting for a helm member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
It's already possible to define `.Spec.Agent.Config.Confd` and `.Spec.Agent.Config.Checksd`, but those options are not propagated to the Clusterchecks Runner. As a runner is basically an agent, we're just reusing the same configuration. This applies the same changes as this proposed change to stable/datadog's Helm chart: helm/charts#23139
It's already possible to define `.Spec.Agent.Config.Confd` and `.Spec.Agent.Config.Checksd`, but those options are not propagated to the Clusterchecks Runner. As a runner is basically an agent, we're just reusing the same configuration. This applies the same changes as this proposed change to stable/datadog's Helm chart: helm/charts#23139
It's already possible to define `.Spec.Agent.Config.Checksd`, but that option is not propagated to the Clusterchecks Runner. As a runner is basically an agent, we're just reusing the same configuration. This applies the same changes as this proposed change to stable/datadog's Helm chart: helm/charts#23139
It's already possible to define `.Spec.Agent.Config.Checksd`, but that option is not propagated to the Clusterchecks Runner. As a runner is basically an agent, we're just reusing the same configuration. This applies the same changes as this proposed change to stable/datadog's Helm chart: helm/charts#23139
It's already possible to define `.Spec.Agent.Config.Checksd`, but that option is not propagated to the Clusterchecks Runner. As a runner is basically an agent, we're just reusing the same configuration. This applies the same changes as this proposed change to stable/datadog's Helm chart: helm/charts#23139
It's already possible to define `.Spec.Agent.Config.Checksd`, but that option is not propagated to the Clusterchecks Runner. As a runner is basically an agent, we're just reusing the same configuration. This applies the same changes as this proposed change to stable/datadog's Helm chart: helm/charts#23139
/ok-to-test |
It's already possible to define `checksd` and in the Agent config, but those options are not propagated to the Clusterchecks Runner. As a runner is basically an agent, we're just reusing the same configuration. Signed-off-by: Julio Greff <julio.greff@datadoghq.com>
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: juliogreff, L3n41c The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…elm#23139) It's already possible to define `checksd` and in the Agent config, but those options are not propagated to the Clusterchecks Runner. As a runner is basically an agent, we're just reusing the same configuration. Signed-off-by: Julio Greff <julio.greff@datadoghq.com> Signed-off-by: Adrien Loiseau <adrien.loiseau@logic-immo.com>
It's already possible to define `.Spec.Agent.Config.Checksd`, but that option is not propagated to the Clusterchecks Runner. As a runner is basically an agent, we're just reusing the same configuration. This applies the same changes as this proposed change to stable/datadog's Helm chart: helm/charts#23139
…elm#23139) It's already possible to define `checksd` and in the Agent config, but those options are not propagated to the Clusterchecks Runner. As a runner is basically an agent, we're just reusing the same configuration. Signed-off-by: Julio Greff <julio.greff@datadoghq.com> Signed-off-by: Miguel Mingorance <miguel.mingorance@deliveryhero.com>
What this PR does / why we need it:
It's already possible to define
checksd
andconfd
in the Agentconfig, but those options are missing for the Clusterchecks Runner.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]
[stable/mychartname]
)