docs(runpod): clarify that runPod status JSON omits the pod spec - #700
Merged
xavpaice merged 1 commit intoAug 12, 2026
Merged
Conversation
✅ Deploy Preview for troubleshoot-sh ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Member
Author
|
Release replicatedhq/troubleshoot#2105 prior to merge |
kriscoleman
approved these changes
Aug 12, 2026
xavpaice
deleted the
xavpaice/sc-139179/runpod-collector-exposes-sensitive-pod-spec
branch
August 12, 2026 02:34
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Updates the runPod collector docs to clarify that /[collector-name]/[collector-name].json contains pod metadata and status, but not the Spec, so sensitive data from podSpec (env vars, commands, args, image pull secrets, etc.) is not persisted in the bundle.