-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CONTP-683] feat[beta]: Support injecting APM and Dogstatsd sockets using CSI volumes instead of hostpath volume #34828
[CONTP-683] feat[beta]: Support injecting APM and Dogstatsd sockets using CSI volumes instead of hostpath volume #34828
Conversation
Test changes on VMUse this command from test-infra-definitions to manually test this PR changes on a VM: dda inv aws.create-vm --pipeline-id=58053470 --os-family=ubuntu Note: This applies to commit bbbcaa2 |
Uncompressed package size comparisonComparison with ancestor Diff per package
Decision |
Static quality checks ✅Please find below the results from static quality gates Successful checksInfo
|
[BETA] Add support for mounting Datadog CSI Volumes instead of hostpath | ||
volumes in the admission controller config webhook. This applies | ||
to mounting Dogstatsd and Tracing UDS sockets onto user applications. | ||
This requires datadog CSI driver to be installed and running on the cluster. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if we should put a releasenote here given that the datadog CSI driver is not yet publicly released.
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: a3816f5 Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | quality_gate_logs | % cpu utilization | +3.83 | [+1.01, +6.65] | 1 | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +0.94 | [+0.07, +1.81] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | +0.46 | [+0.40, +0.51] | 1 | Logs bounds checks dashboard |
➖ | file_tree | memory utilization | +0.45 | [+0.35, +0.55] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | +0.31 | [-0.47, +1.09] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | +0.15 | [-0.62, +0.93] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | +0.13 | [-0.34, +0.61] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | +0.02 | [-0.79, +0.84] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.01 | [-0.01, +0.03] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | +0.00 | [-0.63, +0.63] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | -0.00 | [-0.81, +0.81] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | -0.00 | [-0.82, +0.81] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.01 | [-0.30, +0.28] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | -0.01 | [-0.70, +0.68] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | -0.08 | [-0.13, -0.03] | 1 | Logs bounds checks dashboard |
➖ | tcp_syslog_to_blackhole | ingress throughput | -0.99 | [-1.06, -0.92] | 1 | Logs |
Bounds Checks: ✅ Passed
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
✅ | file_to_blackhole_0ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency_linear_load | memory_usage | 10/10 | |
✅ | file_to_blackhole_100ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_100ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_300ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_300ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_500ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_500ms_latency | memory_usage | 10/10 | |
✅ | quality_gate_idle | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | intake_connections | 10/10 | |
✅ | quality_gate_logs | lost_bytes | 10/10 | |
✅ | quality_gate_logs | memory_usage | 10/10 |
Explanation
Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%
Performance changes are noted in the perf column of each table:
- ✅ = significantly better comparison variant performance
- ❌ = significantly worse comparison variant performance
- ➖ = no significant change in performance
A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".
For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.
-
Its configuration does not mark it "erratic".
CI Pass/Fail Decision
✅ Passed. All Quality Gates passed.
- quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved with suggestions, I see that the release note may be deleted anyway, but wanted to offer revisions just in case. Thanks!
--- | ||
features: | ||
- | | ||
[BETA] Add support for mounting Datadog CSI Volumes instead of hostpath |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[BETA] Add support for mounting Datadog CSI Volumes instead of hostpath | |
[PREVIEW] Add support for mounting Datadog CSI Volumes instead of hostpath |
- | | ||
[BETA] Add support for mounting Datadog CSI Volumes instead of hostpath | ||
volumes in the admission controller config webhook. This applies | ||
to mounting Dogstatsd and Tracing UDS sockets onto user applications. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to mounting Dogstatsd and Tracing UDS sockets onto user applications. | |
to mounting Dogstatsd and tracing UDS sockets onto user applications. |
I'm not sure about this one, ignore if you're not using "tracing" in the general sense
[BETA] Add support for mounting Datadog CSI Volumes instead of hostpath | ||
volumes in the admission controller config webhook. This applies | ||
to mounting Dogstatsd and Tracing UDS sockets onto user applications. | ||
This requires datadog CSI driver to be installed and running on the cluster. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This requires datadog CSI driver to be installed and running on the cluster. | |
This requires the Datadog CSI driver to be installed and running on the cluster. |
[BETA] Add support for mounting Datadog CSI Volumes instead of hostpath | ||
volumes in the admission controller config webhook. This applies | ||
to mounting Dogstatsd and Tracing UDS sockets onto user applications. | ||
This requires datadog CSI driver to be installed and running on the cluster. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[BETA] Add support for mounting Datadog CSI Volumes instead of hostpath | |
volumes in the admission controller config webhook. This applies | |
to mounting Dogstatsd and Tracing UDS sockets onto user applications. | |
This requires datadog CSI driver to be installed and running on the cluster. | |
[BETA] Add support for mounting Datadog CSI volumes instead of hostpath | |
volumes in the admission controller config webhook. This applies | |
to mounting DogStatsD and tracing TDS sockets onto user applications. | |
This requires Datadog CSI driver to be installed and running on the cluster. |
If you do decide to include this release note, here are some styleguide edits!
releasenotes-dca/notes/support-csi-volume-in-dca-config-webhook-bb75ea7b0a81c3fe.yaml
Outdated
Show resolved
Hide resolved
…k-bb75ea7b0a81c3fe.yaml Co-authored-by: Wassim Dhif <[email protected]>
@@ -227,7 +244,7 @@ func injectExternalDataEnvVar(pod *corev1.Pod) (injected bool) { | |||
return | |||
} | |||
|
|||
func buildVolume(volumeName, path string, hostpathType corev1.HostPathType, readOnly bool) (corev1.Volume, corev1.VolumeMount) { | |||
func buildHostPathVolume(volumeName, path string, hostpathType corev1.HostPathType, readOnly bool) (corev1.Volume, corev1.VolumeMount) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: readOnly
seem to always be true
, if there is not potential use case of it being false
, it should probably be removed from the function signature.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer to keep it as it is because it makes it easier in the future to support other use cases without it adding significant complexity to the code.
@@ -246,3 +263,27 @@ func buildVolume(volumeName, path string, hostpathType corev1.HostPathType, read | |||
|
|||
return volume, volumeMount | |||
} | |||
|
|||
func buildCSIVolume(volumeName, path string, injectionMode csiInjectionMode, readOnly bool, csiDriver string) (corev1.Volume, corev1.VolumeMount) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: readOnly seem to always be true, if there is not potential use case of it being false, it should probably be removed from the function signature.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as above
/merge |
View all feedbacks in Devflow UI.
The median merge time in
|
What does this PR do?
Currently, UDS sockets for DSD and APM are injected into user apps in the form of hostpath volumes thanks to the config webhook.
We support two types of hostpath volumes:
This PR allows configuring the admission controller to leverage the existence of a CSI driver to replace HostPath volumes by CSI volume.
This feature requires the datadog CSI driver to be deployed and running on the cluster.
The CSI volume will take into account the user's choice (Socket vs DirectoryOrCreate) when injecting the CSI driver and will provide the same behaviour in the CSI driver via the
mode
attribute set in the volumeAttributes.Motivation
Allow users to use dogstatsd and APM tracing over UDS in namespaces having baseline or restrictive pod security standards. (CSI volumes are accepted in such contexts, hostpath volumes are not).
Describe how you validated your changes
Deploy the datadog csi driver
docker build
.helm install --set image.repository=<image-name> --set image.tag=<tag> datadog-csi ./chart/datadog-csi-driver
Deploy the agent with dca
Deploy a test app
Once all agents (including the cluster agent) are up and running, create a test app in the dev namespace:
Verify CSI Volume Injection
Check the deployment pods and verify that they got CSI volumes injected and mounted:
Notice the mode of the volumes is
socket
, and the path is the socket file path.They should be mounted like this:
Verify custom metrics
Check the UI and verify that the app is able to send custom metrics:

Verify that
Uninstall the aget and delete the test app, then try again the same test while removing
DD_ADMISSION_CONTROLLER_INJECT_CONFIG_TYPE_SOCKET_VOLUMES: "true"
.The effect should be that the injected CSI volume should have mode
local
and have pathvar/run/datadog
Possible Drawbacks / Trade-offs
Additional Notes