Introduce a k8s based lading example #1622
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
Author
scottopell
reviewed
Dec 3, 2025
| name: lading-config | ||
| namespace: default | ||
| data: | ||
| lading.yaml: | |
Contributor
There was a problem hiding this comment.
JFYI - this could also be passed in as LADING_CONFIG, inlining lading config in a k8s manifest was my original motivation to support
lading/lading/src/bin/lading.rs
Lines 277 to 281 in 268a16a
This commit demonstrates how one might use lading in a k8s environment to determine the memory bounds for a target container, in this case Datadog Agent. The example used here is harsh and comes from Datadog Agent's own Regression Detector experiment `uds_dogstatsd_to_api`. Run like so: ``` ./k8s/experiment.sh --total-limit 1200 --agent-memory 700 --trace-memory 100 --sysprobe-memory 300 --process-memory 100 --duration 600 --tags "purpose:smp-experiment,agent-limit:2048" ``` This invocation demostrates a memory allocation that works for Agent under these conditions, results: ``` ======================================== RESULT: SUCCESS ======================================== No restarts detected Test duration: 600 seconds Tags: purpose:smp-experiment,agent-limit:2048 Container memory usage: agent: 640.67 MB / 700 MB (91.5%) trace-agent: 31.36 MB / 100 MB (31.4%) system-probe: 266.26 MB / 300 MB (88.8%) process-agent: 48.00 MB / 100 MB (48.0%) TOTAL: 986.29 MB / 1200 MB (82.2%) ``` Instructions are present in the `k8s/README.md` for changing lading's configuration and Datadog Agent's own configuration. Signed-off-by: Brian L. Troutwine <brian.troutwine@datadoghq.com>
blt
force-pushed
the
blt/introduce_a_k8s_based_lading_example
branch
from
c0fb66b to
2fd183a
Compare
|
Hi Brian, our team is looking at the PR and Will come back soon with their first experiences using it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This commit demonstrates how one might use lading in a k8s environment to determine the memory bounds for a target container, in this case Datadog Agent. The example used here is harsh and comes from Datadog
Agent's own Regression Detector experiment
uds_dogstatsd_to_api.Run like so:
This invocation demonstrates a memory allocation that works for Agent under these conditions, results:
Instructions are present in the
k8s/README.mdfor changing lading's configuration and Datadog Agent's own configuration.